On 9/8/08, Oliver Kullmann <O.Kullmann at swansea.ac.uk> wrote:
> 1. With the first file "Batch.mac" Maxima hangs,
> and one has to kill it:
>
> (%i1) batch("Batch.mac");
>
> batching /home/csoliver/SAT-Algorithmen/OKplatform/Batch.mac
> (%i2) for x in [1,2,3] do print(x)
> 1
> 2
> 3
> Evaluation took 0.0000 seconds (0.0002 elapsed) using 4.250 KB.
> (%o2) done
I tried that batch file with Maxima post-5.16 + Clisp 2.46, ECL recent
sources, GCL 2.6.7, and CMUCL 19c. In each case I get the above
output, plus it appears to echo the final space on a line by itself,
then it waits for console input. If I enter 0; then it displays 0 as expected.
What kind of a system do you have? What versions of Clisp and ECL
are you working with?
> 2. And with the second file "Unless.mac" Maxima shows a
> parse failure and thus ignores the function "fun":
>
> (%i1) batch("Unless.mac");
>
> batching /home/csoliver/SAT-Algorithmen/OKplatform/Unless.mac
> (%i2)
>
> Maxima encountered a Lisp error:
>
> CAR: $FOUND is not a list
When I try this with Clisp 2.46 + Maxima post-5.16, fun is defined
correctly and I don't see an error.
Try running maxma -l clisp -g . After the error happens, try entering :bt
to get a backtrace. Post the backtrace and I'll take a look at it.
Does it change things any if the variable found is renamed to
something different?
Robert Dodier