On 3/11/07, Andreas Eder <aeder at arcor.de> wrote:
> Error summary:
> Error found in rtestnset, problem:
> (error break)
> Error found in rtest16, problem:
> (error break)
> Error found in rtest_mset, problem:
> (error break)
It looks like changes I made to src/mlisp.lisp (defstruct stuff, more
on that later) have caused a very puzzling behavior ...
The errors detected above are from reading expressions after
string(...), but only when running in test mode.
E.g. with the following 2-line batch file
$ cat /tmp/6.mac
string(123);
abc;
then batch("/tmp/6.mac") => success, but batch("/tmp/6.mac", test) =>
Maxima encountered a Lisp error:
READ-CHAR-NO-HANG: argument (#\3 #\2 #\1) is not a stream
Automatically continuing.
To reenable the Lisp debugger set *debugger-hook* to nil.
Maxima encountered a Lisp error:
NO-APPLICABLE-METHOD: When calling #<STANDARD-GENERIC-FUNCTION CLOSE>
with arguments ((#\3 #\2 #\1) :ABORT T), no method is applicable.
The changes to mlisp were not intended to have any effect
on the parser. At this point I'm baffled. I'll investigate later today.
Sorry for the bother.
Robert