Everyone should switch to my calendar, in which the leap day is February 28b.
To set my watch, I had to enter time, date, and year. It doesn’t display the year, but it didn’t surprise me in the least when I got up this morning and it was reading 2-29. Previous years it just gone to March 1 after Feb. 28.
Reminds me of 4 years ago when everyone’s Playstation 3 went apeshit because one of the internal calendars didn’t recognize 2/29 but something else on the system did.
edit:whoop, my bad, it was because the system thought 2010 WAS a leap year when it wasn’t
For the most part, programmers shouldn’t be adding numbers to dates. They should be using date addition functions, which are widely available and carefully tested for all sorts of tricky situations like leap years and DST. They also usually require less application code than doing it the hard way.
Dear old Dad turns 23 today.
This, essentially.
Cecil Himself expounds.
The Pirates of Penzance? I’ve often heard that.
Or the hobbit calendar, in which Mid-Year’s Day belongs to no week or month (and so every year has the same calendar) and nor does the leap day, which is called “Overlithe” and comes the day after Mid-Year’s Day.
There’s also a Sherlock Holmes story that uses this plot device. This Scottish guy is 80 years old, but still hasn’t received an inheritance that he’s supposed to get in the year of his 21st birthday.
Oh yeah, this takes place in the year 1900, which makes things even more messed up, because nobody remembers until the last minute that century years aren’t leap years.
While spending months coding Y2K changes, I asked my boss if I should add code to allow for that as long as I was there anyway. He said, “No, no one will be using this COBOL code in 2100.” They’re still using it today, so we’ll see.
That’s usually true, but remember that in the Gregorian Calendar, century years that are divisible by 400 are leap years. So the year 1900 was not a leap year, but the year 2000 was a leap year.
Say what, now? Every presidential election year is a leap year. Isn’t it? Is there some special break on century years?
Edit: Just read the wiki and now robby’s here to report the results.
[QUOTE=psychonaut]
But presumably the federal government didn’t issue his driver’s licence, so the OP’s scenario wouldn’t apply in this case.
[/QUOTE]
The federal government didn’t issue the license, but they control just about every possible aspect of all states’ licenses, other than the colors.
The Department of State also has no problems whatsoever with 2/29 birthdays when they issue passports.
As usual for talk radio, what the OP’s boss describes is utter bunk.
This has turned out to be much more interesting than I expected. But, buried in the OP, is a question; Does the federal government require the parents to choose to enter either Februrary 28 or March 1, not Februrary 29 on the baby’s birth certificate?
Seems to me that would be depriving someone born on that of a pretty unique document and a cool talking point.
And don’t forget to add/subtract hours if you were born in a different time zone. 
Does the federal government issue many birth certificates? That’s really the province of the states. Perhaps on military base hospitals abroad? I’m not sure what standards apply there.
U.S. territories seem to have their local territory government responsible for issuing birth certificates rather than the feds.
The Geniuses at Microsoft had a Leap Year bug cause an outage for their Azure cloud service. /cue hooting from all the Apple & Linux fanboys and gurls.
Do you mean often, as in frequently?
No, never. Well, hardly ever.
if((year % 4 == 0 && year % 100 != 0) || year % 400 == 0)
return 1; /* leap */
else
return 0; /* no leap */
Thanks, Buttercup.