Article View: comp.lang.lisp.x
Article #326YAXB (Yet Another Xlisp Bug)
From: Tom Almy
Date: Sun, 30 Jun 1991 18:11
Date: Sun, 30 Jun 1991 18:11
24 lines
1371 bytes
1371 bytes
While working on a Microsoft Windows port (which requires better internal file management -- to be friendly files have to be temporarily closed while not being accessed) I discovered YAXB: If an error occurs during the execution of LOAD, the file gets left open. This means that file handles are consumed. The result of this is after about a dozen failed loads (in the MS-DOS environment) there are no more available handles. The solution to this appears to be that LOAD needs a built-in "unwind-protect". I'll post a fix in a week or so. A byproduct of this port is that some future "release" will keep track of file names -- file streams print as "#<Input-Stream "afile.xyz">" instead of the original, cryptic "#<File-Stream: 1f03b210>". I also have successfully gotten XLISP to run using the MS-DOS medium memory model. Tom Almy toma@sail.labs.tek.com Standard Disclaimers Apply -- Tom Almy toma@sail.labs.tek.com Standard Disclaimers Apply
Technical Details
Message-ID:
<9834@sail.LABS.TEK.COM>Path:
arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!zephyr.ens.tek.com!tekgen!sail!tomaShow Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!zephyr.ens.tek.com!tekgen!sail!toma From: toma@sail.LABS.TEK.COM (Tom Almy) Newsgroups: comp.lang.lisp.x Subject: YAXB (Yet Another Xlisp Bug) Message-ID: <9834@sail.LABS.TEK.COM> Date: 30 Jun 91 18:11:56 GMT Reply-To: toma@sail.LABS.TEK.COM (Tom Almy) Organization: Tektronix, Inc., Beaverton, OR. Lines: 24