Hi John,
On 5/29/2015 12:44 PM, 'John Clements' via Racket Users wrote:
> On May 28, 2015, at 1:53 PM, George Neuner <gneun...@comcast.net> wrote:
> I did see the message from John Clements. I'm not a Racket developer,
> but superficially it appears to me that the negative delay values John
> found should be causing errors on every platform that supports file
> locking [which is every supported platform]. Clearly they aren't, so
> now I am wondering whether locking actually is enabled and being used
> for local filesystems.
I don’t think I would interpret my message in that way. Specifically, I was
unable to find a call to that function that specified those values (delay or
max-delay) at all. However, I was exploring using github, and didn’t take the
time to actually download the 6.1.1 tarball. My guess (and it’s just a guess)
is that there is such a call, and that the problem does ultimately stem from
some problem that’s specific to NFS.
Sorry I misunderstood. It sounded as if you had found calls with (maybe
unset variable?) delays that would violate the contract.
George
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
