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

DEFMAX being autoloaded

    Date: 27 December 1979 04:50-EST
    From: Jeffrey P. Golden <JPG at MIT-MC>
	    . . . 				 MAXOUT;GRAMI > and 
    MAXOUT;GRAMO >  are generated by "splitting" MRG;GRAM > via the 
    file MRG;SPLIT > , function SPLITFILE in the latter file.  
    It is possible that the unfortunate loading of the DEFMAX stuff can 
    be prevented by the resetting of some switch when splitting MRG;GRAM > .
    . . . 
I've edited the one line necessary into MRG;GRAM >, and will leave it to you
to redo the splitting and rebuilding of MACSYMA.  the needed line is
	(declare  (setq defmacro-displace-call () ))
    Date: 27 December 1979 04:36-EST
    From: Jeffrey P. Golden <JPG at MIT-MC>
    Why does L^K  (LOAD '|MACSYM;GRAMI FASL|)  cause the DEFMAX 
    stuff to be loaded in?  [Ignore the error message about MDISPATCH 
    which occurs afterwards.]  After all this is a FASL file!  The 
    previous version of MACSYM;GRAMI FASL (which I can retrieve from tape 
    if such is desired) did not require the loading in of the DEFMAX stuff 
    while creating a new version of MACSYMA.
In case you are still wondering, if you use DEFMACRO with intention
of using any of the MACROMEMO features at runtime, then you need the
runtime support package (which is only about 333. words); the default
is to have DEFMACRO-DISPLACE-CALL non-null, but you clearly don't want
to be bothered with that for the two little macros MATCH and TELL.