Brooklyn Enterprise
The Enterprise Baseball Club of Brooklyn was part of the National Association of Base Ball Players (NABBP) in the 1860s. The Enterprise Club first began playing other members of the NABBP in the 1850s.
Players
- Bob Ferguson
- Greg Norton
- Dickey Pearce
Games
| Date | Opponent | Score | Win/Loss/Tie | Location* |
|---|---|---|---|---|
| November 20, 1856 | National Club | 24-12 | Win | NA |
| August 10, 1860 | Newark Eurekas | 25-21 | Win | NA |
| August 24, 1860 | New York Gothams | 15-56 | Loss | Hoboken |
| August 27, 1860 | Newark Eurekas | 13-21 | Loss | NA |
| August 29, 1860 | New York Gothams | 15-21 | Loss | Brooklyn |
| June 5, 1861 | Brooklyn Eckfords | 19-53 | Loss | Bedford, Brooklyn |
| July 10, 1861 | Newark Eurekas | 5-27 | Loss | NA |
| August 20, 1861 | New York Gothams | 13-14 | Loss | Hoboken |
| July 26, 1864 | New York Gothams | 13-22 | Loss | Hoboken |
| June 6, 1865 | New York Gothams | 18-19 (19 innings) | Loss | Hobokn |
| June 16, 1866 | Morrisania Union | 16-42 | Loss | Morrisania, The Bronx |
| September 14, 1866 | Brooklyn Excelsior | 18-16 | Win | NA |
| September 19, 1866 | Waterbury | 37-21 | Win | Hoboken |
- Note- Based on games recorded in Peverelly's book and baseballlibrary.com.
gollark: PETA will destroy you.
gollark: At least it has generics.
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
gollark: It also does have the whole "anything which implements the right functions implements an interface" thing, which seems very horrible to me as a random change somewhere could cause compile errors with no good explanation.
References
Freyer, John and Mark Rucker. "Peverelly's National Game." Dover, New Hampshire: Arcadia Publishing: 2005. ISBN 0-7385-3404-8
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.