@bytebro So the fourteenth of March is Pi day in the US - 3/14.
Here (in *cough* Europe) it would be erm 3/14 so the the third of quatuordecember.
If you think that is odd, note that December means "tenth month" (novem is nine, octem is eight, septem is seven) and mildly curse a Roman emperor from 2000 odd years ago for being a dick.
July is named after Julius Caesar and August is named after Augustus Caesar.
Wait until Trump gets himself worked up to JC levels of wankery!
Like it. Also, several people have pointed out that in the UK/EU, PI day would be July 22, and 22/7 is a better approximation of PI than 3.14. Eat your American Pi and enjoy! π
@bytebro What's wrong with 31 April (31-4) in the civilized world?
If push comes to shove, we right pond types could probably come up with a forty first month and barely blush at a four hundred and forty first month.
Let's face it: a bunch of us (them over there, the French mob) invented a centimetre which is exactly 2.54 times too short, but exactly 100th of a metre, which is superb.
Bring it on!
@bytebro I was hoping you would note that 141 months was a bit odd for a year and elide me adding a day to an inconspicuous month.
OK, got the memo. We'll have to do our own thing on this one 8)
Oh our calendar is clearly 'odd', and fairly obviously in today's world 'silly'.
But it is what it is, so one either goes with a Julian date (number of days) for moderately historical stuff, or perhaps Unix Epoch (numbers of seconds) although that might become problematic in Jan 2038, depending on your sizeof(time_t)?
Personally, if a date is ever going to be 'stored', I would use an extended ISO format, so "2026-03-15T01:00:10Z" at UTC with or without an offset for timezones.