|
Re: :reload when machine clock is ahead of file-system clock: msg#00017lang.haskell.glasgow.bugs
On 2004-08-11 at 16:17PDT Mike Gunter wrote: > > For me, :reload often seems to treat an out-of-date interpreted module > as up-to-date. I think this is a consequence of my machine clock > being ahead of my file-system clock. > > I believe this behavior results from the use of getClockTime as the > linkableTime for interpreted modules. It seems more correct to use > the mtime of the source. In general, it seems best not to compare > local-machine times and file-system times. Surely nowadays one uses ntp, so the times on the two machines are accurate? Jón -- Jón Fairbairn Jon.Fairbairn@xxxxxxxxxxxx
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | :reload when machine clock is ahead of file-system clock, Mike Gunter |
|---|---|
| Next by Date: | RE: :reload when machine clock is ahead of file-system clock, Simon Marlow |
| Previous by Thread: | :reload when machine clock is ahead of file-system clock, Mike Gunter |
| Next by Thread: | RE: :reload when machine clock is ahead of file-system clock, Simon Marlow |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |