> The word length for the z80 was / is 8 bits, yet it could still cope with
> large numbers and relatively large discs. People seem to have latched onto
> 64 bit as a cure-all.

Yes, the architecture does not have to be 64 bit, but the time_t. How the 64
bit number is calculated is irrevelant. This problem could also be solved if
time_t related lib functions counts the dates from 2000 for example and not
from 1970, but I am not sure if that is the best solution. Then someone will
say "what if a software wants to go back in time...".

Tamas




On Sat, Apr 19, 2008 at 10:37 PM, sergio masci <smplx@allotrope.net> wrote:

>
>
> On Sat, 19 Apr 2008, Vasile Surducan wrote:
>
> > How many computers built 30 years ago are still used right now ?
> > In 2038 will be no computer in use manufactured today.
> > Joe, this subject is a waste of EE time...
> > :)
>
> The architecture has nothing to do with this.
>
> The word length for the z80 was / is 8 bits, yet it could still cope with
> large numbers and relatively large discs. People seem to have latched onto
> 64 bit as a cure-all. I would expect this from the average PC end user who
> knows next to nothing about software or hardware, but come on I thought
> most of the people on this list had a bit more sense.
>
> The biggest problems we will face in 2038 will be can we find all the
> source, compilers, linkers, libraries etc needed to rebuild an app and
> will the average programmer know the difference between an integer and a
> string :-)
>
> Regards
> Sergio
> --
> http://www.piclist.com PIC/SX FAQ & list archive
> View/change your membership options at
> http://mailman.mit.edu/mailman/listinfo/piclist
>



-- 
Rudonix DoubleSaver
Did You Know that DoubleSaver is Smaller and More Powerful FailSafe Device
than Any Other You can Get?
http://www.rudonix.com
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist