[m-rev.] for review: smart recompilation

[Peter Schachte]

On Sat, Jun 02, 2001 at 11:26:38PM +1000, Fergus Henderson wrote:
> On 30-May-2001, Peter Schachte <schachte at cs.mu.OZ.AU> wrote:
> > > As far as I can tell, the only other alternative is to pass timestamps
> > > around as type `tm', or as strings formatted as above, rather than
> > > `time_t'.
> > 
> > How about as an integer number of seconds since the epoch, UCT?
> 
> If you use a Mercury `int' for that, and choose 1970 as the epoch,
> then on 32-bit architectures you'll have a Y2.038K problem.
> 
> This could be avoided by using a Mercury `integer', or a Mercury `float'.
> 
> P.S.
> Many operating systems (e.g. Windows, Solaris 2.8) now support sub-second
> resolution on their file timestamps, so ideally we should support that.

Actually, I was thinking of 1 Jan 2000 as the epoch for Mercury, which would
make it a Y2.068K problem, but using a float would probably be better.

-- 
Peter Schachte <schachte at cs.mu.OZ.AU>  Dost thou love life? Then do not
http://www.cs.mu.oz.au/~schachte/      squander time, for that's the stuff
Phone:  +61 3 8344 9166                life is made of.
Fax:    +61 3 9348 1184                    -- Benjamin Franklin 
--------------------------------------------------------------------------
mercury-reviews mailing list
post:  mercury-reviews at cs.mu.oz.au
administrative address: owner-mercury-reviews at cs.mu.oz.au
unsubscribe: Address: mercury-reviews-request at cs.mu.oz.au Message: unsubscribe
subscribe:   Address: mercury-reviews-request at cs.mu.oz.au Message: subscribe
--------------------------------------------------------------------------