> I could have used "return (unsigned int)-1;" which automatically gets
> converted to either 0xFFFFFFFF or 0xFFFFFFFFFFFFFFFF according to the
> size of an int, but I thought that not everybody would have understood
> it, and so preferred to the long way with a warning (which next time
> I should maybe write in capitals, so that it does not go unnoticed).
> 

The problem is that a 32 bits unsigned int (0xFFFFFFFF) can be happily
casted into a 64-bits time_t and the result will be >0.

time_t is defined as 'long long'.

Vincent

Reply via email to