But when lispargs is complicated, this doesn't actually pass the
desired lispargs correctly. For example for cmucl, we want to do
```
lispargs="-noinit -nositeinit -eval '(setf *gc-verbose* nil *default-external-format* :utf8)' -eval '(set-system-external-format :utf8 :utf8)' -load $catprogname -eval '(quit)'"
```
But the actual args are parsed in an unexpected way. This can be tested
via this simple program
```
#include <stdio.h>
int
main(int argc, char **argv)
{
int i;
for (i = 0; i < argc; i++) printf("argv[%d]='%s'\n", i, argv[i]);
return 0;
}
```
```
Note that the `(setf *gc-verbose* nil)` is broken up into 3 separate
args which is not what we want. It should be just one arg, which is
the arg to `-eval`. What we really want is:
```
argv[0]='./args'
argv[1]='-noinit'
argv[2]='-nositeinit'
argv[3]='-eval'
argv[4]='(setf *gc-verbose* nil *default-external-format* :utf8)'
argv[5]='-eval'
argv[6]='(set-system-external-format :utf8 :utf8)'
argv[7]='-load'
argv[8]='-eval'
argv[9]='(quit)'
```
To fix this, we add a `runlisp` function to run the lisp with the
desired args. And instead of putting all the args into lispargs, we
just call runlisp after deciding which lisp is being used and just
append the desired args to the runlisp command.
ce29527...
by
Wolfgang Dautermann <email address hidden>
In the description for dlsode_step and dlsode_init, add a cross-ref to
the section "Getting Started with ODEPACK" to help users figure out
where to go to learn how to use the functions.
Also fixed a typo, and added @math{} to a couple of places to make it
typeset a bit nicer.
fdc7b4a...
by
Wolfgang Dautermann <email address hidden>
Windows installer: Update wxWidgets.
b68360c...
by
Wolfgang Dautermann <email address hidden>
Add quit() with an exit code to the german documentation.
Quit takes an optional integer that is used as the exit code from
maxima.
* src/suprv1.lisp
* Add optional exit-code arg for $quit; this calls bye with the
given code.
* src/utils.lisp
* Add optional exit-code arg to bye. This calls the appropriate
implementation-specific function with the exit-code if possible.
Otherwise it's ignored.
* doc/info/Command.texi
* Update docs to mention the optional exit-code
*
b7e2cf1...
by
Wolfgang Dautermann <email address hidden>
The examples just randomly start after the table, which is weird. So,
add an intro sentence to separate the end of the table and the
beginning of the examples.
