>>20
The file could also be shrunk, renamed, unlinked, edited in the same size, have its NFS mount connection go down, or have any number of other things happen to it. In the absence of a function provided by MIT Scheme that doesn't require a size and reads the entire file, whatever its size happens to be, I felt that chasing all these race conditions was pointless, because the proper solution would be for MIT Scheme to provide that function. If it already does, I missed it. You are, however, entitled to feel differently and provide a more robust function that loops on reading chunks into a growing buffer until EOF, as the race condition you pointed out is certainly a real one.