[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[no subject]

    Date: 20 July 1980 03:39-EDT
    From: Kent M. Pitman <KMP at MIT-MC>
    Subject: Typo in SHARPM
    . . . I note that /#-CNTRL-META-IFY has a bug in it. The line that claims 
    to extract the C-M- bits actually only extracts M-bits. You probably want 
    CADDR instead of CADR. -kmp
Fixed.  tnx muchly.
    Date: 20 July 1980 03:47-EDT
    From: Kent M. Pitman <KMP at MIT-MC>
    From "NILCOM;SHARPM >" ...
	(comment NIL-type defsharps for maclisp)
	#-NIL  (progn 'COMPILE 
    Shouldn't that be #+NIL ...? NIL-/#-MACRO-DATALIST seems to get set up even
    in non-NIL environments currently -- that seems like a waste ...
Definetly not.  The idea is that general maclisp code has to be able to support
a minimal abount of NIL-type defsharps so that things like
   '(a #-NIL frob #N #B"101011" c)
can even be read in.  ALAN's suggestion was used here - namely the code
for these defshaprs will live, but is activated (thru the use of the varialbe
NIL-/#-MACRO-DATALIST) only when under a #N conditinal;  in a pseudo-NIL
environment (like the NIL simulator, or NILAID), more serious defsharping
takes place.  The extra burden for maclisp to be able to pass over #N code
is only about a 10% increast to the SHARPM package.
    Date: 20 July 1980 03:44-EDT
    From: Kent M. Pitman <KMP at MIT-MC>
    but /#-MACRO-DATALIST is initially unbound. I am uncomfortable with this.
    Is there some reason it can't be () by default? In fact, why does it have
    privileged status as a system symbol when |#-C-M-bits| and some of the 
    other variables used by SHARPM do not? -kmp
It could be initially set to () with no harm -- was probably left this way
during some experimentation as to how much should be assembled in and how
much should be autoloaded.