[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[no subject]
- To: (BUG LISPM) at MIT-MC
- Subject:
- From: JPG@MIT-MC
- Date: Sat ,12 Aug 79 12:54:19 EDT
CC: CWH at MIT-MC, JPG at MIT-MC
Moon@MIT-AI 08/12/79 12:43:36
To: (BUG LISPM) at MIT-AI
CC: (BUG MACSYMA) at MIT-AI
Macsyma should not be loaded with INHIBIT-FDEFINE-WARNINGS. Only by chance
did I discover a new system function it was clobbering. Any conflicts between
Macsyma files ought to be resolved, since they are making Macsyma bigger on the
10 by duplicating function definitions. In any case these can be ignored
easily by typing P to the FDEFINE warning. Any conflicts between Macsyma
and the lisp machine system are BUGS!!! They should be fixed, not ignored.
Generally either the EXTERNAL list or the SHADOW list of the package
declaration needs to be fixed, depending on whether or not Macsyma is
supposed to be redefining that function.
I of course have nothing to do with the setup for MACSYMA on the LISP
machine. I would like to point out that I am aware of no duplicate
function definitions in MACSYMA, and that we fix them whenever they
occur. (There are cases of macros and functions which intentionally
have the same names. Macros are only used at compile time in MACSYMA,
and duplicating some of them with compatible functions has helped
greatly when MACSYMA programmers have been careless. Also, the user
has a choice sometimes between alternate but similar packages, e.g.
POIS2 and POIS3. I believe all of these cases have simple solutions
on the LISP machine.)