Dunno whether this helps...
I haven't looked at the pertinent Racket code, but errors like this
often happen in Unix applications because the mtime of the file is in
the future relative to the current time clock. Less commonly, because
the mtime changed since the file was read by the app or since the app
last checked.
The most common case can happen because a VC/CM system is updating the
times (someone mentioned Git, and some other systems do this), because
it's a network filesystem and the server and workstation clocks aren't
synced sufficiently, or because NTP or some other mechanism dangerously
jumped the current time clock in reverse (usually a good NTP daemon will
slow the clock rather than jump in reverse).
Robby Findler wrote at 02/26/2011 01:39 PM:
Looking at the code, I don't see anything suspicious (assuming that
after-save-file and file-or-directory-modify-seconds work properly, that is).
--
http://www.neilvandyke.org/
_________________________________________________
For list-related administrative tasks:
http://lists.racket-lang.org/listinfo/dev
