[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
"bare" lisp and AUTOLOAD properties
- To: JONL at MIT-MC
- Subject: "bare" lisp and AUTOLOAD properties
- From: George J. Carrette <GJC at MIT-MC>
- Date: Tue, 17 Feb 81 18:31:00 GMT
- Cc: BUG-LISP at MIT-MC, JPG at MIT-MC
- Original-date: 17 February 1981 13:31-EST
Date: 17 FEB 1981 1319-EST
From: JONL (Jon L White)
cc: (BUG LISP), JPG
Re: "bare" lisp and AUTOLOAD properties
There is of course a trade-off here between inconvenience to
the "naive" maclisp user, and the address-starved Macsyma.
I would maintain that what one gets with a :LISP is not suitable
for the "naive" maclisp user and that there is in fact no such trade off;
why should :LISP get one a cold-load environment?
but it's not clear what of the current autoloadables should
be flushed, even if there were the opportunity to flush
enough to make up 1K of space.
By setting up the mechanisms for this, that is, by making it policy that
the "working lisp" for naive users is thoughtfully constructed by
FASLOADing into the "cold load" lisp, we gain flexibility, and perhaps
even lift ourselves out of the gutter of worrying about
"one more symbol does or does not go over a page boundary".
In other words, I'm saying flush EVERYTHING which is not referenced
by COMPILED code. This includes UREAD et. al. and doesn't this amount
to something significant?