[m-rev.] for review: smart recompilation

[Fergus Henderson]

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.

-- 
Fergus Henderson <fjh at cs.mu.oz.au>  |  "I have always known that the pursuit
                                    |  of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh>  |     -- the last words of T. S. Garp.
--------------------------------------------------------------------------
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
--------------------------------------------------------------------------