Waldek Hebisch <[EMAIL PROTECTED]> writes: | CY wrote: | > Confirmed - builds on sbcl and clisp. Wow! Thanks Waldek! | > | > I don't know if it's important, but I am getting a lisp readout when | > using the integration package: | > | > (2) -> integrate(sin(x),x) | > [loading messages] | > /home/cyapp/mathtoplevel/axiomtoplevel/testwork/wh-sandbox/target/i686-pc- | > linux/algebra/COMPLEX.fasl | > for domain Complex | > | > | > ; in: LAMBDA NIL | > ; (VMLISP:QCAR BOOT::|#1|) | > ; --> CAR | > ; ==> | > ; (THE CONS BOOT::|#1|) | > ; | > ; caught WARNING: | > ; undefined variable: |#1| | > | | AFAICS this comes because Axiom uses eval and sbcl by default | compiles all evals. I am investigating whether the warning | indicate some real problem. One can silence warning switching | to interpreted eval (which will be done for different reasons | in next revision):
There is a questionable habit in the Axiom core source code of defining variables through SETQ -- that tends to trigger warnings from several Lisp implementations. Is it possible that the above is such a warning? (the |#1| are names for synthetized lambdas). -- Gaby _______________________________________________ Axiom-developer mailing list Axiom-developer@nongnu.org http://lists.nongnu.org/mailman/listinfo/axiom-developer
