Content-Transfer-Encoding: |
7bit |
Sender: |
|
Subject: |
|
From: |
|
Date: |
Mon, 8 May 2000 00:20:30 EDT |
Content-Type: |
text/plain; charset="US-ASCII" |
MIME-Version: |
1.0 |
Reply-To: |
|
Parts/Attachments: |
|
|
[log in to unmask] wrote:
>The C programming language has standard libraries for converting
>time in secs since 1970 to date, and vice-versa. The file structures
>usually have the "time last accessed" as this 32-bit number. Converting
>to a 64-bit compiler is great, but your OS and file structure might be
>still affected.
>
>So this affects only C and Unix, Right? Alas no, it affects a lot of
>Operating Systems that have C components. Like Windows 95, 98,
>NT, and I think 2000, also Win 3.11, in fact, a significant propoportion
>of the world's computers. Of Macs I know not, but it wouldn't surprise
>me if they had the same problem on some versions of their OS's,
>especially the ones with significant bits of Unix in them (via Next).
The Macintosh calling interface provides for the expression
of tens of thousands of years. What they do internally is
something they might have to fix some time, but that is
rather easier than making users change.
|
|
|