>>>>> "Richard" == Richard Fateman <fateman@cs.berkeley.edu> writes:
Richard> Insisting that the underlying CL be ANSI will
Richard> not solve ALL porting problems, since some of the code in Maxima
Richard> is not and cannot be ANSI -- there are pieces that we use that have
Richard> not been standardized. Thus foreign function code is
Richard> not in ANSI. I'm not sure what else we really need that
Richard> is not specified in ANSI CL. Does anyone have a list?
I didn't mean to imply that everything would work if it were all
ANSI. But core Maxima would probably work if that were true. The
fancy stuff would have to be implementation specific.
As far as I know, Maxima wants access to the shell environment
variables and wants to be able to run subshells for plotting. There
are some assumptions that the file system looks somewhat Unix-like.
Can probably remove most of this dependency by using logical
pathnames.
I don't think there's any foreign function code except for CMUCL to
get regexp support. We can remove this and use some of the Lisp
regexp implementations out there, if necessary.
Ray