Skip to content

Comment on Microsoft confirms Exchange Year 2022 problemparent

Comments

Perhaps switch to unsigned int until a sane solution is implemented. Should give them a couple thousand years to work with.

No, it just kicks the can down the road another 22 years.

At first glance thought they were using yyyy format, it's actually only yy. You are correct.

It's pretty likely they'll change the data type somehow, but I guess the question is how fast they can test how that interacts with everywhere that might encounter that variable. Presumably the hack they implemented here buys them at least a month or two to test a real code change.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.