Fred Sayer
Fred Sayer (6 June 1913 – 7 April 1972) was an Australian rules footballer who played with Hawthorn in the Victorian Football League (VFL).[1]
| Fred Sayer | |||
|---|---|---|---|
| Personal information | |||
| Full name | Fred Sayer | ||
| Date of birth | 6 June 1913 | ||
| Date of death | 7 April 1972 (aged 58) | ||
| Original team(s) | Scotch College | ||
| Playing career1 | |||
| Years | Club | Games (Goals) | |
| 1933–34 | Hawthorn | 7 (4) | |
|
1 Playing statistics correct to the end of 1934. | |||
| Sources: AFL Tables, AustralianFootball.com | |||
Notes
- Holmesby, Russell; Main, Jim (2014). The Encyclopedia of AFL Footballers: every AFL/VFL player since 1897 (10th ed.). Seaford, Victoria: BAS Publishing. p. 787. ISBN 978-1-921496-32-5.
gollark: Excitingly, minoteaur crashes when closing the database if migrating it if and only if it is not run under valgrind.
gollark: I can't point to a particular build/project tooling system which *utterly* doesn't fail for me. makefiles fail unfathomably sometimes, cmake fails unfathomably lots of the time, cargo sometimes runs into bizarre dependency errors, nimble works fine actually but I don't ever install stuff from it, luarocks is no, python has an awful mess, etc.
gollark: > In a typical build system, the dependency arrows go down. Although this is the way they would naturally go due to gravity, it is unfortunately also where the enemy's gate is. This makes it very inefficient and unfriendly. In tup, the arrows go up. This is obviously true because it rhymes. See how the dependencies differ in make and tup:Wow, this sounds like a great build system.
gollark: It's a rough measure of project size/complexity.
gollark: Possibly a ten-thousandth.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.