[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: WGD at MIT-MC, RWK at MIT-MC
- Subject: Buggy XLISP
- From: JONL at MIT-MC (Jon L White)
- Date: Thu, 12 Feb 81 17:19:00 GMT
- Cc: (BUG LISP) at MIT-MC
- Original-date: 12 FEB 1981 1219-EST
Incidentally, since last Saturday, the "newer" lisp had been placed as
LISP^K, so XLISP^K is again experimental.
Date: 10 February 1981 19:55-EST
From: William G. Dubuque <WGD at MIT-MC>
LISP;EXTEND fails to load into an XL, dying trying to call 0
(actually its when EXTSFA is being loaded). Congratulations, that's
every day now for the past two weeks that some piece of the system has
LISP^K and XLISP^K, although same version numbers, should have been different
dumps when you got this problem, and you shouldn't have seen it in LISP^K.
RWK's fix is correct, mentioned in
Date: 11 February 1981 02:46-EST
From: Robert W. Kerns <RWK at MIT-MC>
Subject: Problems with XLISP
The problem with EXTEND and EXTSFA and YESNOP not loading is due to
GENTEMP not working which is in turn due to EXPLODEN being broken, giving
FXPDL OUT OF PHASE for fixnums, and ILOPR at location 0 for flonums.
. . .
I have fixed and patched the problem.
However this patch should be installed only as XLISP^K, due to the
fact that I was still trying to get the bug out of PUTPROP referenced as
Date: 10 February 1981 17:53-EST
From: Jon L White <JONL at MIT-MC>
Subject: Lightening Strikes Twice!
. . .
Sigh, remember the PUTPROP twice bug that has plagued us lo these
6 years? This is still another manifestation of it. I've done some
more work on PUTPROP, but it still isn't completely bug-free . . .
So I hope this "experimental" PUTPROP doesn't cause any problems --
they would be manifest when pure-loading up a big system (like,
COMPLR, NILAID or MACSYMA!)