1945 William & Mary Indians football team

The 1945 William & Mary Indians football team represented William & Mary during the 1945 college football season.

1945 William & Mary Indians football
ConferenceSouthern Conference
1945 record6–3 (4–2 SoCon)
Head coachRube McCray (2nd year)
Home stadiumCary Field
1945 Southern Conference football standings
Conf  Overall
TeamW L T  W L T
No. 13 Duke $ 4 0 0  6 2 0
No. 19 Wake Forest 4 1 1  5 3 1
William & Mary 4 2 0  6 3 0
Clemson 2 1 1  6 3 1
Maryland 3 2 0  6 2 1
VMI 3 2 0  5 4 0
North Carolina 2 2 0  5 4 0
NC State 2 4 0  3 6 0
VPI 2 5 0  2 6 0
South Carolina 0 3 2  2 4 3
Richmond 0 4 0  2 6 0
  • $ Conference champion
Rankings from AP Poll

Schedule

DateOpponentSiteResult
September 29Catawba*W 19–6
October 6at Tennessee*
L 13–48
October 13vs. VPIW 38–0
October 20vs. VMIW 13–9
October 27vs. NC State
L 6–20
November 3at MarylandW 33–14
November 10vs. North Carolina
L 0–6
November 17Merchant Marine*W 25–7
November 22at RichmondW 33–0
  • *Non-conference game

NFL Draft selections

= Pro Football Hall of Fame = Canadian Football Hall of Fame = College Football Hall of Fame
NFL Draft Selections 
# Year Round Pick Overall Name Team Position
10 1946 10 8 88 Al Vandeweghe Philadelphia Eagles End
11 1946 11 3 93 Doc Holloway Pittsburgh Steelers Guard
12 1946 16 8 148 Buddy Hubbard Philadelphia Eagles Back
13 1946 20 8 188 Dave Butcher Philadelphia Eagles Back
gollark: Okay, sure, you can ignore that for Go itself, if we had Go-with-an-alternate-compiler-but-identical-language-bits it would be irrelevant.
gollark: I can't easily come up with a *ton* of examples of this, but stuff like generics being special-cased in for three types (because guess what, you *do* actually need them), certain basic operations returning either one or two values depending on how you interact with them, quirks of nil/closed channel operations, the standard library secretly having a `recover` mechanism and using it like exceptions a bit, multiple return values which are not first-class at all and which are used as a horrible, horrible way to do error handling, and all of go assembly, are just inconsistent and odd.
gollark: And inconsistent.
gollark: But... Google is hiring some of the smartest programmers around, can they *not* make a language which is not this, well, stupid? Dumbed-down?
gollark: It has some very nice things for the cloud-thing/CLI tool/server usecase; the runtime is pretty good and for all garbage collection's flaws manual memory management is annoying, and the standard library is pretty extensive.

References


    This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.