Prev: Stack overflow question
Next: Driver finder program said -"missing 25!!!"
From: VanguardLH on 9 Aug 2010 16:33
Unknown wrote:

> At exactly 06 minutes and 07 seconds after 5 o'clock on August 9th of this
> year it will be 05:06:07 08/09/10 ~ This will not happen again until the
> year 3010.

Only if you use mm/dd/yy (and only 2 digits for yy) for the datestamp
format. Of course, sorting on that format means sorting by month
instead of by day. Obviously a bad sorting format. I'm sure other
nonsensical or historical formats could come up with another sequence.
The logical format would be yy/mm/dd (to also match the hh:mm:ss format
you used) for sorting. That means it won't be until 10/11/12 (Nov 12,
2010) at either at 07:08:09 (hh:mm:ss) AM or PM when the sequence you
infer will occur. As for not reoccuring until 3010, well, that
obviously reoccurs every 1000 years when using only 2 digits for the
year.

Of course, in another thousand years, we'll still be using Windows XP
for your post to be on-topic here assuming newsgroups are still around
then, too. Uh huh.
From: Antares 531 on 9 Aug 2010 16:39
On Mon, 9 Aug 2010 16:15:04 -0400, "Twayne" <nobody(a)spamcop.net>
wrote:

>In news:pp206612ke6m4ftn5v4tjijj93rosumar2(a)4ax.com,
>Antares 531 <gordonlrDELETE(a)swbell.net> typed:
>> On Mon, 9 Aug 2010 08:52:21 -0500, "Unknown"
>> <unknown(a)unknown.kom> wrote:
>>
>>>
>>> At exactly 06 minutes and 07 seconds after 5 o'clock on
>>> August 9th of this year it will be 05:06:07 08/09/10 ~
>>> This will not happen again until the year 3010.
>>>
>> How about 06:07:08 09/10/11, or are you saying the sequence
>> must start with 05:06:07
>
>He said
>05:06:07 08/09/10 ~
> will not happen again until the year 3010.
>
>Read it.
>
Thanks, but I read it and still wasn't sure if he meant the exact
number sequence or a similar number sequence. He said "it" and "this"
which could mean "this exact number system" or it could mean "a number
sequence such as this."
From: Barry Schwarz on 10 Aug 2010 00:40
On Mon, 9 Aug 2010 08:52:21 -0500, "Unknown" <unknown(a)unknown.kom>
wrote:

>
>At exactly 06 minutes and 07 seconds after 5 o'clock on August 9th of this
>year it will be 05:06:07 08/09/10 ~ This will not happen again until the
>year 3010.

Why wouldn't the same date and time in 2110 produce the same result?

--
Remove del for email
From: Patok on 10 Aug 2010 01:30
Barry Schwarz wrote:
> On Mon, 9 Aug 2010 08:52:21 -0500, "Unknown" <unknown(a)unknown.kom>
> wrote:
>
>> At exactly 06 minutes and 07 seconds after 5 o'clock on August 9th of this
>> year it will be 05:06:07 08/09/10 ~ This will not happen again until the
>> year 3010.
>
> Why wouldn't the same date and time in 2110 produce the same result?

Indeed it will. But it will still be wrong. Ignoring the century,
this serial phenomenon will happen on 2010-09-08, 07:06:05; that is,
September 8, 7am.
If we don't ignore the century, the phenomenon falls on 2019-18-17,
16:15:14, that is, June 17, 2020, 4pm. :)
--
You'd be crazy to e-mail me with the crazy. But leave the div alone.
--
Whoever bans a book, shall be banished. Whoever burns a book, shall burn.
From: Bob I on 10 Aug 2010 08:04


Patok wrote:

> Barry Schwarz wrote:
>
>> On Mon, 9 Aug 2010 08:52:21 -0500, "Unknown" <unknown(a)unknown.kom>
>> wrote:
>>
>>> At exactly 06 minutes and 07 seconds after 5 o'clock on August 9th of
>>> this year it will be 05:06:07 08/09/10 ~ This will not happen again
>>> until the year 3010.
>>
>>
>> Why wouldn't the same date and time in 2110 produce the same result?
>
>
> Indeed it will. But it will still be wrong. Ignoring the century, this
> serial phenomenon will happen on 2010-09-08, 07:06:05; that is,
> September 8, 7am.
> If we don't ignore the century, the phenomenon falls on 2019-18-17,
> 16:15:14, that is, June 17, 2020, 4pm. :)

Look again, I think you have a few typos. ;-)

First  |  Prev  | 
Pages: 1 2
Prev: Stack overflow question
Next: Driver finder program said -"missing 25!!!"