A repost?
-
I thought every developer and his dog knew about this. :doh:
Cheers, Vikram.
"...we are disempowered to cultivate in their communities an inclination to assimilate to our culture." - Stan Shannon.
Vikram A Punathambekar wrote:
I thought every developer and his dog knew about this.
Dogs have better things to do than worrying about Y! Messenger.
Nobody can give you wiser advice than yourself. - Cicero ப்ரம்மா
-
I thought every developer and his dog knew about this. :doh:
Cheers, Vikram.
"...we are disempowered to cultivate in their communities an inclination to assimilate to our culture." - Stan Shannon.
-
If Yahoo Messenger is still in use in 2038 that'd be more worrying than a stupid crash! :)
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*) -
FWD: Note: This is just for FYI only, Please Don't try this. This is true and if you do this then your network based applications will not work. The Year 2038 Problem Test it now. steps... 1. login to yahoo messenger 2. send instant message to anyone - fine its working... 3. now, change ur system date to 19-Jan-2038, 03:14:07 AM or above 4. Confirm weather ur date is changed 5. again send instant message to anyone... Your YM crahes.... * * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * * Why..... What is it? * * Starting at GMT 03:14:07, Tuesday, January 19, 2038, It is expected to see lots of systems around the world breaking magnificently: satellites falling out of orbit, massive power outages (like the 2003 North American blackout), hospital life support system failures, phone system interruptions, banking errors, etc. One second after this critical second, many of these systems will have wildly inaccurate date settings, producing all kinds of unpredictable consequences. In short, many of the dire predictions for the year 2000 are much more likely to actually occur in the year In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run. This can result in incorrect and wildly inaccurate dates being reported by the operating system and/or applications. The effect of this bug is hard to predict, because many applications are not prepared for the resulting "skip" in reported time anywhere from 1901 to a "broken record" repeat of the reported time at the second the bug occurs. Also, may make some small adjustment to the actual time the bug expresses itself. This bug to cause serious problems on many platforms, especially Unix and Unix-like platforms, because these systems will "run out of time". What causes it? Time_t is a data type used by C and C++ programs to represent dates and times internally. (Windows programmers out there might also recognize it as the basis for the CTime and CTimeSpan classes in MFC.) time_t is actually just an integer, a whole number, that counts the number of seconds since January 1, 1970 at 12:00 AM Greenwich Mean Time. A time_t value of 0 would be 12:00:00 AM (exactly midnight) 1-Jan-1970, a time_t value of 1 would be 12:00:01 AM (one second after midnight) 1-Jan-1970, etc.. some example times and their exact time_t representations: Date & time time_t representation 1-Jan-1970, 12:00:00 AM GMT 0
You are the first person in the history of the planet to discover this problematic date. All 6.5 billion of us thank you effusively.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
-
You are the first person in the history of the planet to discover this problematic date. All 6.5 billion of us thank you effusively.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
:BOW: Hey but you know why I asked if it's a repost? I vaguely remembered me posting the same few years before!.But vaguely. lol! The catch is that Yahoo had released successive versions of the messenger and all of them still crash!
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir? **Dr.Brad :**Well,I just replied to everything Graus did and then argued with Negus for a bit.
-
Meat Loaf wrote:
Someone's still using it
Me. :sigh:, coz clients use yahoo.
-Prakash
-
:BOW: Hey but you know why I asked if it's a repost? I vaguely remembered me posting the same few years before!.But vaguely. lol! The catch is that Yahoo had released successive versions of the messenger and all of them still crash!
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir? **Dr.Brad :**Well,I just replied to everything Graus did and then argued with Negus for a bit.
They don't expect it (at least the versions they are releasing now) to be in use in 2038.
-------- Micrologic Networks, India
-
They don't expect it (at least the versions they are releasing now) to be in use in 2038.
-------- Micrologic Networks, India
-
Meat Loaf wrote:
Someone's still using it
Me. :sigh:, coz clients use yahoo.
-Prakash
-
If Yahoo Messenger is still in use in 2038 that'd be more worrying than a stupid crash! :)
Regards, Nish
Nish’s thoughts on MFC, C++/CLI and .NET (my blog)
Currently working on C++/CLI in Action for Manning Publications. (*Sample chapter available online*) -
FWD: Note: This is just for FYI only, Please Don't try this. This is true and if you do this then your network based applications will not work. The Year 2038 Problem Test it now. steps... 1. login to yahoo messenger 2. send instant message to anyone - fine its working... 3. now, change ur system date to 19-Jan-2038, 03:14:07 AM or above 4. Confirm weather ur date is changed 5. again send instant message to anyone... Your YM crahes.... * * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * * Why..... What is it? * * Starting at GMT 03:14:07, Tuesday, January 19, 2038, It is expected to see lots of systems around the world breaking magnificently: satellites falling out of orbit, massive power outages (like the 2003 North American blackout), hospital life support system failures, phone system interruptions, banking errors, etc. One second after this critical second, many of these systems will have wildly inaccurate date settings, producing all kinds of unpredictable consequences. In short, many of the dire predictions for the year 2000 are much more likely to actually occur in the year In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run. This can result in incorrect and wildly inaccurate dates being reported by the operating system and/or applications. The effect of this bug is hard to predict, because many applications are not prepared for the resulting "skip" in reported time anywhere from 1901 to a "broken record" repeat of the reported time at the second the bug occurs. Also, may make some small adjustment to the actual time the bug expresses itself. This bug to cause serious problems on many platforms, especially Unix and Unix-like platforms, because these systems will "run out of time". What causes it? Time_t is a data type used by C and C++ programs to represent dates and times internally. (Windows programmers out there might also recognize it as the basis for the CTime and CTimeSpan classes in MFC.) time_t is actually just an integer, a whole number, that counts the number of seconds since January 1, 1970 at 12:00 AM Greenwich Mean Time. A time_t value of 0 would be 12:00:00 AM (exactly midnight) 1-Jan-1970, a time_t value of 1 would be 12:00:01 AM (one second after midnight) 1-Jan-1970, etc.. some example times and their exact time_t representations: Date & time time_t representation 1-Jan-1970, 12:00:00 AM GMT 0
time_thas been deprecated for a long time. Anyone who is still using it must have rocks in his or her head. MFC 7 and above use_time64_tfor precisely that reason.Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
FWD: Note: This is just for FYI only, Please Don't try this. This is true and if you do this then your network based applications will not work. The Year 2038 Problem Test it now. steps... 1. login to yahoo messenger 2. send instant message to anyone - fine its working... 3. now, change ur system date to 19-Jan-2038, 03:14:07 AM or above 4. Confirm weather ur date is changed 5. again send instant message to anyone... Your YM crahes.... * * * YES ALL NETWORK BASED APPLICATION WILL NOT WORK NOW * * * Why..... What is it? * * Starting at GMT 03:14:07, Tuesday, January 19, 2038, It is expected to see lots of systems around the world breaking magnificently: satellites falling out of orbit, massive power outages (like the 2003 North American blackout), hospital life support system failures, phone system interruptions, banking errors, etc. One second after this critical second, many of these systems will have wildly inaccurate date settings, producing all kinds of unpredictable consequences. In short, many of the dire predictions for the year 2000 are much more likely to actually occur in the year In the first month of the year 2038 C.E. many computers will encounter a date-related bug in their operating systems and/or in the applications they run. This can result in incorrect and wildly inaccurate dates being reported by the operating system and/or applications. The effect of this bug is hard to predict, because many applications are not prepared for the resulting "skip" in reported time anywhere from 1901 to a "broken record" repeat of the reported time at the second the bug occurs. Also, may make some small adjustment to the actual time the bug expresses itself. This bug to cause serious problems on many platforms, especially Unix and Unix-like platforms, because these systems will "run out of time". What causes it? Time_t is a data type used by C and C++ programs to represent dates and times internally. (Windows programmers out there might also recognize it as the basis for the CTime and CTimeSpan classes in MFC.) time_t is actually just an integer, a whole number, that counts the number of seconds since January 1, 1970 at 12:00 AM Greenwich Mean Time. A time_t value of 0 would be 12:00:00 AM (exactly midnight) 1-Jan-1970, a time_t value of 1 would be 12:00:01 AM (one second after midnight) 1-Jan-1970, etc.. some example times and their exact time_t representations: Date & time time_t representation 1-Jan-1970, 12:00:00 AM GMT 0
-
time_thas been deprecated for a long time. Anyone who is still using it must have rocks in his or her head. MFC 7 and above use_time64_tfor precisely that reason.Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
-
time_thas been deprecated for a long time. Anyone who is still using it must have rocks in his or her head. MFC 7 and above use_time64_tfor precisely that reason.Anna :rose: Linting the day away :cool: Anna's Place | Tears and Laughter "If mushy peas are the food of the devil, the stotty cake is the frisbee of God"
Anna-Jayne Metcalfe wrote:
MFC 7 and above use _time64_t for precisely that reason.
then we have to wait till 20038 to see Yahoo Messenger crash :)
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers, Alok Gupta VC Forum Q&A :- I/ IV Support CRY- Child Relief and You
-
:BOW: Hey but you know why I asked if it's a repost? I vaguely remembered me posting the same few years before!.But vaguely. lol! The catch is that Yahoo had released successive versions of the messenger and all of them still crash!
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir? **Dr.Brad :**Well,I just replied to everything Graus did and then argued with Negus for a bit.
VuNic wrote:
I fadely remembered me posting the same few years before!.
VuNic, I think the word you are looking for is vaguely.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
-
VuNic wrote:
I fadely remembered me posting the same few years before!.
VuNic, I think the word you are looking for is vaguely.
Michael Martin Australia "I controlled my laughter and simple said "No,I am very busy,so I can't write any code for you". The moment they heard this all the smiling face turned into a sad looking face and one of them farted. So I had to leave the place as soon as possible." - Mr.Prakash 24/04/2004
-
I thought every developer and his dog knew about this. :doh:
Cheers, Vikram.
"...we are disempowered to cultivate in their communities an inclination to assimilate to our culture." - Stan Shannon.
-
You are the first person in the history of the planet to discover this problematic date. All 6.5 billion of us thank you effusively.
--Mike-- Visual C++ MVP :cool: LINKS~! Ericahist | PimpFish | CP SearchBar v3.0 | C++ Forum FAQ Ford, what's this fish doing in my ear?
Michael Dunn wrote:
You are
Mike didn't you really see the "FWD" at the first line? :sigh:
Press: 1500 to 2,200 messages in just 6 days? How's that possible sir? **Dr.Brad :**Well,I just replied to everything Graus did and then argued with Negus for a bit.
-
Pah, but they're just not thinking of the implications of what'll happen some time in March in the year 292271025015!!! Do these people never learn?
There are solutions, e.g. this: RFC 2550 [^] :-D
RFC 2550 wrote:
As discussed in 2.4.1, the end of the universe is predicted to occur well before the year 10 ** 30. However, if there is one single lesson to be learned from the current Y2K problems, it is that specifications and conventions have a way of out living their expected environment. Therefore we feel it is imperative to completely solve the date representation problem once and for all.
-
Pah, but they're just not thinking of the implications of what'll happen some time in March in the year 292271025015!!! Do these people never learn?