java.util.Timer not handling negative System.currentTimeMillis()

Fri Nov 25 07:36:00 GMT 2005

Tom,
> Martin> I know this is an obscure problem, but is there is requirement
> Martin> that we are only "allowed" to run gcj on targets with clocks >
> Martin> 1970.
>> The portability code isn't fully spec'd out to this level. The code
> is the only guide.
>> Martin> For now I will just make sure the time is not less than 1970
> Martin> and larger than some other limit overflowing the long.
>> Martin> The problem arises because my target's RTC comes with an undefinded 
> Martin> initial time - hence anything is possible :-)

> Yeah, you should probably initialize this sometime before initializing
> libgcj. It seems to me that this randomness would preclude a workable
> libgcj patch... ?

I've done that too...
But maybe, someday, someone would try to use libgcj on a device, where 
the value of RTC is of no matter, and when trying to schedule a 
TimerTask he would be rather confused... Although rather unlikely :-)
// Martin