[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- To: (BUG LISP) at MIT-MC
- Subject: FASL-NAMELIST
- From: REES at MIT-MC (Jonathan A. Rees)
- Date: Tue, 8 Jan 80 07:03:00 GMT
- Original-date: 8 JAN 1980 0203-EST
(By the way, all you hackers out there, in case you're curious,
this issue arose in the first place because it was desired to
subsume responsibility for printing the "WARNING! FOO, A USER SUBR AT 12345,
IS BEING REDEFINED AS A LSUBR BY FASL FILE DSK:LOSER;LOSE FASL"
that FASLOAD so courteously provides; this feature lets you get a
handle on the name of the fasl file, which is otherwise (and unfairly)
I agree with KMP, that this properly belongs as a subfunction of
STATUS. Also, this idea occurs to me: why not have LOAD put the
namelist in this place whether the file is being FASLOADed or not?
Thus in RWK's FOOBAR example (appropriately hacked), doing
(LOAD '((RWK) FOOBAR >)) would print ((DSK RWK) FOOBAR 23) [substitute
correct version number], but (LOAD '((RWK) FOOBAR)) would print
((DSK RWK) FOOBAR FASL). This makes the hirsute eval-mungibles's
jobs slightly less ponderous. I guess in this case the result is the
same as you'd get with (TRUENAME INFILE). One gritty problem:
shouldn't this guy get bound/unbound through calls to recursive
calls to LOAD/FASLOAD?
Suggestion for name: (STATUS LDNAM) or (STATUS LDFNA). The MIDAS
symbol for this is LDFNAM.