Microsoft and Y10K compliance?
-
No I'm really not that funny but the NSA sensors all my output and by the time they get done it's funny. :)
VS2010/Atmel Studio 6.1 ToDo Manager Extension The problem with the gene pool is that there is no lifeguard. -Steven Wright
Mike Hankey wrote:
but the NSA sensors censor all my output
FTFY. :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
Mike Hankey wrote:
but the NSA sensors censor all my output
FTFY. :) /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
Thanks Ravi, I've been battling with multiple embedded sensor problems since yesterday so must have been a Freudian slip. (I don't know what he was doing wearing a slip though) :)
VS2010/Atmel Studio 6.1 ToDo Manager Extension The problem with the gene pool is that there is no lifeguard. -Steven Wright
-
Thanks Ravi, I've been battling with multiple embedded sensor problems since yesterday so must have been a Freudian slip. (I don't know what he was doing wearing a slip though) :)
VS2010/Atmel Studio 6.1 ToDo Manager Extension The problem with the gene pool is that there is no lifeguard. -Steven Wright
To be honest, I often slip up myself. ;P /ravi
My new year resolution: 2048 x 1536 Home | Articles | My .NET bits | Freeware ravib(at)ravib(dot)com
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
:doh: :laugh:
Getting information off the Internet is like taking a drink from a fire hydrant. - Mitchell Kapor
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
Perhaps this is proof that Microsoft Research is working on Time Travel! ;)
-
Thanks Ravi, I've been battling with multiple embedded sensor problems since yesterday so must have been a Freudian slip. (I don't know what he was doing wearing a slip though) :)
VS2010/Atmel Studio 6.1 ToDo Manager Extension The problem with the gene pool is that there is no lifeguard. -Steven Wright
I presume it was his better half: Fruedian Slip[^]
"If you don't fail at least 90 percent of the time, you're not aiming high enough." Alan Kay.
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
Don't worry. If you like your four-digit years, you can keep them. Period.
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
Ah, memories. I spent way more time answering customers' inquiries about Y2K compliance than I did analyzing for potential issues. We did not have any failure of systems once 2000 arrived. I did let customers know of the potential issue in our programs that would happen in 2038 (C's 32-bit time overflows), but I also indicated we expected to have a new version out by then. :) Prior to Y2K was the concern about Sept. 9, 1999, which when represented as 9999, might be interpreted as an "end of data" marker. I remember explaining to one employee that such date codes would be six digits long, with zeroes, because of the need for two digits in each of the month and day. Of course, that brings us back to the year before Y10K; will the year 9999 pose problems in legacy code?
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
Well, they have a lot of time to get this right, but by then, we may all be using Google Neural Implant devices.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
I'm always looking at this page cause I don't always remember all the off the wall date formats. I found this! http://msdn.microsoft.com/en-us/library/8kb3ddd4.aspx#yyyyySpecifier[^] So their Y10K compliant as far as formatting a date? But anything over 9999 blows up. Guess MS has a little bit more work to do on Y10K compliance? Hopefully they get it done on time!
I expect that before we reach the year 10,000 we will switch to the universal date format as used by most of the alien planets we have visited. Also as 1 year is the time it takes the Earth to travel round the Sun, the length of a year will be the tine the planet Zog takes to travel round it's star. If I am wrong, then please let me know in the year 10,001ad.
