Path: utzoo!utgpu!watmath!iuvax!cica!tut.cis.ohio-state.edu!CIS.OHIO-STATE.EDU!welch
From: welch@CIS.OHIO-STATE.EDU (Arun Welch)
Newsgroups: comp.sys.xerox
Subject: interlisp/loops compiler bug ??
Message-ID: <8908071429.AA26071@saqqara.cis.ohio-state.edu>
Date: 7 Aug 89 14:29:33 GMT
References: <EHO.89Aug6234038@bogey.Princeton.EDU>
Organization: Info-1100 Mailing List
Lines: 12

This isn't a compiler bug, but rather a "network bug" (in quotes
'cause it's not really a bug). What's happening is that the compiler
is compiling a particularly large hunk of code, and isn't blocking
long enough for the packets to get through to the file server.  The
file server sees that there aren't any packets for a while, and
decides that the dlion went off the net, so it closes the connection.
Meanwhile the dlion finishes compiling, wants to write those bytes out
to the server and finds that it's connection is closed, thus
producing the error. As far as I know, there's no fix for it but to
compile on the local disk and copy the file over to the file server.

...arun