Regarding Maxima and Allegro Common Lisp 6.2:
I tried, on a different computer, the current CVS tarball.
it redefines WHILE in cl-info which is not allowed.
it redefines // which is not allowed (in clmacs-cl)
I don't know what is needed... shadowing of some sort?
;; (run) now fails with symptoms shown below...
it uses STORE in a way that allegro doesn't like in
spgcd. I rewrote swap-rows to use aref and setf.
(defun SWAP-ROWS (mat m n) ;Interchange row m and n
(do ((k 0 (f1+ k))
(l (ncols mat)))
((> k l) mat)
(setf (aref mat m k)
(prog2 0 (aref mat n k)
(setf (aref mat n k) (aref mat m k))))))
ACL requires that nparse.lisp be read in before it
can be compiled. Otherwise one gets
While compiling (:TOP-LEVEL-FORM "nparse.lisp" 27961):
Error: attempt to call `LED-PROPL' which is an undefined function.
[condition type: UNDEFINED-FUNCTION]
The pathname stuff is still wrong
and after editing src/autoconf-variables.lisp
I suspect that it is not used at all by anything.
Here is what I put in; I did not know what to do with *autoconf-host*
;;; -*- Lisp -*-
;;edited 1/5/04 by RJF
(in-package :maxima)
(defparameter *autoconf-prefix* "c:/maxima/maxima-5.9.0")
(defparameter *autoconf-exec_prefix* "c:/maxima/maxima-5.9.0")
(defparameter *autoconf-package* "maxima")
(defparameter *autoconf-version* "5.9.0")
(defparameter *autoconf-libdir* "c:/maxima/maxima-5.9.0/lib")
(defparameter *autoconf-libexecdir* "c:/maxima/maxima-5.9.0/libexec")
(defparameter *autoconf-datadir* "c:/maxima/maxima-5.9.0/share")
(defparameter *autoconf-infodir* "c:/maxima/maxima-5.9.0/info")
;;(defparameter *autoconf-host* "i686-pc-linux-gnu")
(run)
Maxima 5.9.0 http://maxima.sourceforge.net
Distributed under the GNU Public License. See the file COPYING.
Dedicated to the memory of William Schelter.
This is a development version of Maxima. The function bug_report()
provides bug reporting information.
Bad file spec: ?C\:\/\/\.maxima\/\#\#\#\.\{fasl\,lisp\,lsp\}
-- an error. Quitting. To debug this try DEBUGMODE(TRUE);)
T
....
(defun $file_search(&rest x) nil)
Warning: $FILE_SEARCH, :OPERATOR was defined in mload.lisp and is now being
defined at the top level
[1] CL-MACSYMA(10): (run)
Maxima restarted.
(C1) x+log(x);
Error: attempt to call `//' which is an undefined function.
[condition type: UNDEFINED-FUNCTION]
There are also
hundreds of compile-time warning messages about proclaims being in
the wrong place in a file,
unused variables, labels,
undefined functions, names assumed global (undeclared),
redefined functions (or macros),
redefined variable values..
All these problems individually are very minor, and even collectively
they do not indicate any fundamental issue. Some of the warnings
presumably should be heeded even in other lisps.
RJF
James Amundson wrote:
>On Tue, 2003-12-30 at 21:43, Richard Fateman wrote:
>
>
>
>>I think that the ACL / linux changes should be merged in
>>to the sourceforge code, and should be safe
>>assuming that is conditionalized correctly. (By the way,
>>how is it that clmacs redefines // ? )
>>
>>
>
>Actually, the cvs version of Maxima has been compatible with ACL for
>quite a while now. I believe it was Ray Toy who did the modifications.
>Unfortunately, I don't think the ACL build has been tested recently, so
>it is possible that something has broken in the meantime. Even so, we
>are at the very least close to ACL compatibility.
>
>
>
>>And what about the file-path stuff?
>>
>>
>
>It isn't clear to me whose problem those are.
>
>
>
>>The conditionalizations for Franz lisp, PDP10, are sad,
>>and presumably haven't been tested in a LONG time.
>>Maybe it's time to cut out some of this.
>>
>>
>
>I wanted to ditch those conditionalizations a long time ago, but was
>voted down. It seems that consensus is building that the time has come
>to do so. We should probably do it in conjunction with the case-fixing
>work. (This is really a discussion for the mailing list, however...)
>
>--Jim
>
>
>
>