[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
suckage
- To: ALAN at MIT-MC
- Subject: suckage
- From: Robert W. Kerns <RWK at MIT-MC>
- Date: Thu, 4 Dec 80 06:48:00 GMT
- Cc: BUG-LISP at MIT-MC, DLW at MIT-MC, MOON at MIT-MC
- Original-date: 4 December 1980 01:48-EST
Date: 4 December 1980 01:26-EST
From: Alan Bawden <ALAN>
Sender: ALAN at CADR3
To: RWK
cc: DLW, MOON, BUG-LISP
Re: suckage
Date: 3 December 1980 22:15-EST
From: Robert W. Kerns <RWK at MIT-MC>
Subject: suckage
To: ALAN at MIT-MC
cc: DLW at MIT-MC, MOON at MIT-MC, BUG-LISP at MIT-MC
Well, 1) *LDB is simply what LDB used to expand into. Blameing it on
MACLISP's SETF is silly, it's what MACROEXPAND produced. Now,
MACLISP's SETF has a DEFSETF for *LDB. So obviously, what happened
here, was that YOUR SETF did a MACROEXPAND, but wasn't prepared to
handle the expansion of LDB.
BULLSHIT. This was in a vanilla lisp. ONLY my defstruct was loaded, and
as I said before it only generates code using LDB and DPB (and SETF of LDB
and DPB).
OK, let's try again. It's STILL SILLY to blame SETF. However, reading DLW's
original complaint again, I find he complained that *DPB was an undefined
function. Now, at this point it should be obvious that SETF expanded and
returned the result, namely *DPB, which is a LEGITIMATE result. So obviously
DLW caught things in some inconsistant state, HAVING NOTHING TO DO WITH SETF,
where *DPB wasn't defined. But I apologize for blaming it on your SETF.