|
:reload when machine clock is ahead of file-system clock: msg#00016lang.haskell.glasgow.bugs
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. thanks, mike
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Non-change in __GLASGOW_HASKELL__ and change to newForeignPtr, Alastair Reid |
|---|---|
| Next by Date: | Re: :reload when machine clock is ahead of file-system clock, Jon Fairbairn |
| Previous by Thread: | Non-change in __GLASGOW_HASKELL__ and change to newForeignPtr, Alastair Reid |
| Next by Thread: | Re: :reload when machine clock is ahead of file-system clock, Jon Fairbairn |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |