On Tue, Apr 11, 2006 at 11:16:08PM +0200, Azerion wrote:

Sometimes you have missed just that moment, that moment that will never happen again. It's like being in coma at the millennium-switch, being in the bathroom when you're national team wins the cup and so on.

At Thursday the 4th of may, 2 miunuted and 3 seconds after 1 am, you're clock will point out:

01:02:03 04-05-06

This will never happen again. This generation is unique. I know this is not a place to dump it, but I do it anyway. Have a nice day :-D

The same can be said about `Tue Apr 11 23:49:53 CEST 2006` or any other time. Also people traveling across a timeline could have this moment twice (or not at all). Then also there will be: 06-05-04 03:02:01 This can be a multitude of dates and times. YY MM DD HH MM SS AM/PM MM DD YY DD MM YY It reminds me of a time when I was on a holiday in Bavaria. People were going to get stamps at a certain time so the stamp would read the town (PLZ) date and time as: 8888 8-8-88 8:08 Die Post even had some sort of container-office to help as amany people as possible, I believe. I did not go there. I had better things to do. :-) It al just shows that people are very good at recognising patterns. Sometimes even there were there are none. http://www.gamedev.net/reference/design/features/rollingsadams/figure7-13.jp... However there are some dates that ARE important: 2038/01/19: (03:14:07 GMT) 2**31 seconds from 00:00:00 GMT, Thursday 1st January 1970 (UNIX's birthday). The seconds counter used for date/time information in UNIX and C and C++ will reach 2,147,483,647 - the largest number which can be stored as a 32-bit signed integer. As a result an overflow problem will occur (i.e. the value of the next number is unpredictable). Time differences mean it appears that it will happen earlier in America (22:14:07 US EST, Monday 18th January 2038). There will also be a an additional problem due to a discrepancy of a few seconds between system clocks and astronomical time because the system will not have taken account of leap second adjustments made in the interim period. This may be significant only for a few very specialised systems, but could give rise to difficulties if changes are based on algorithms which do not take this into account. It is understood that the Java programming language (which in many respects closely resembles C++) will not have this problem. More important dates and times on http://www.iee.org/Policy/Areas/SCS/problemdates.cfm houghi -- Nutze die Zeit. Sie ist das Kostbarste, was wir haben, denn es ist unwiederbringliche Lebenszeit. Leben ist aber mehr als Werk und Arbeit, und das Sein wichtiger als das Tun - Johannes Müller-Elmau

On 4/12/06, Azerion wrote:

Sometimes you have missed just that moment, that moment that will never happen again. It's like being in coma at the millennium-switch, being in the bathroom when you're national team wins the cup and so on.

At Thursday the 4th of may, 2 miunuted and 3 seconds after 1 am, you're clock will point out:

01:02:03 04-05-06

Date formats screw these things up, and this is severely off topic. Now if you posted about Unix time 1234567890, it would be slightly closer to the topic (and correct in terms of once in a lifetime), although several years early: 23:31:30 13-02-2009 And don't tell me you were in the bathroom as the once in a lifetime Unix time 1111111111 drifted past at 01:58:31 UTC on March 18, 2005 Peter 'Pflodo' Flodin