Charles Kendle

Charles Edward Compton Kendle (10 February 1875 3 January 1954) was an English first-class cricketer. Kendle was a right-handed batsman who played primarily as a wicketkeeper.

Charles Kendle
Personal information
Full nameCharles Edward Compton Kendle
Born(1875-02-10)10 February 1875
Amesbury, Wiltshire, England
Died3 January 1954(1954-01-03) (aged 78)
Hellingly, Sussex, England
BattingRight-handed
RoleWicketkeeper
RelationsWilliam Kendle (Nephew)
Domestic team information
YearsTeam
19111914Wiltshire
1899Hampshire
Career statistics
Competition FC
Matches 2
Runs scored 27
Batting average 9.00
100s/50s /
Top score 11
Balls bowled
Wickets
Bowling average
5 wickets in innings
10 wickets in match
Best bowling
Catches/stumpings 2/1
Source: Cricinfo, 1 January 2010

Kendle made his first-class debut for Hampshire in 1899 against Leicestershire. Kendle made two first-class appearances for Hampshire in 1899, his second and final first-class match coming against Yorkshire.

In 1911 Kendle joined Wiltshire, making his debut against the Kent Second XI in the Minor Counties Championship. Kendle played five matches for Wiltshire, with his final Minor COunties match coming against the Surrey Second XI in 1914, where the season was curtailed due to the beginning of the First World War.

Kendle died in Hellingly, Sussex, on 3 January 1954.

Family

Kendle's nephew William Kendle also played first-class cricket for Hampshire, representing the club in five first-class matches.

gollark: Perhaps the headers should also store the location of the last header, in case of [DATA EXPUNGED].
gollark: There are some important considerations here: it should be able to deal with damaged/partial files, encryption would be nice to have (it would probably work to just run it through authenticated AES-whatever when writing), adding new files shouldn't require tons of seeking, and it might be necessary to store backups on FAT32 disks so maybe it needs to be able of using multiple files somehow.
gollark: Hmm, so, designoidal idea:- files have the following metadata: filename, last modified time, maybe permissions (I may not actually need this), size, checksum, flags (in case I need this later; probably just compression format?)- each version of a file in an archive has this metadata in front of it- when all the files in some set of data are archived, a header gets written to the end with all the file metadata plus positions- when backup is rerun, the system™ just checks the last modified time of everything and sees if its local copies are newer, and if so appends them to the end; when it is done a new header is added containing all the files- when a backup needs to be extracted, it just reads the end and decompresses stuff at the right offset
gollark: I don't know what you mean "dofs", data offsets?
gollark: Well, this will of course be rustaceous.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.