Testing running subsidiary lisps with multiple Allegros
Pascal J. Bourguignon
pjb at informatimago.com
Tue Jul 7 13:11:43 UTC 2015
Faré <fahree at gmail.com> writes:
> OK, I believe I understand the issue, that I didn't experience before
> because I only ever used but two allegros at most, alisp and mlisp
> from allegro express.
> IIUC, the issue is indeed that test-program doesn't really know which
> allegro variant it's running, and guesses which it is by getting the
> argv0 then assuming that is in the $PATH. That worked well as long as
> there is only one Allegro directory with alisp and mlisp (and possibly
> 8-bit char variants), but that doesn't work with the all-encompassing
> battery of allegro variants that you guys have been using.
> So instead I updated lisp-invocation to be more clever about allegro
> variants (and ecl variants, while we're at it), and it should work
> better now. I also fixed a bug in lisp-invocation in how it detects
> ALLEGRODIR, etc., to be compatible with run-tests.sh.
You would rather test it with:
The functions set-case-mode and convert-mixed-case-symbols, and two
variables *current-case-mode* and *ignore-package-name-case* are
provided for controlling and sensing case modes.
__Pascal Bourguignon__ http://www.informatimago.com/
“The factory of the future will have only two employees, a man and a
dog. The man will be there to feed the dog. The dog will be there to
keep the man from touching the equipment.” -- Carl Bass CEO Autodesk
More information about the asdf-devel