On 12/18/11, Michel Talon <talon at lpthe.jussieu.fr> wrote:
> Le 18 d?c. 2011 ? 23:33, Robert Dodier a ?crit :
>
>> On 12/18/11, Michel Talon <talon at lpthe.jussieu.fr> wrote:
>>> if [ "$MAXIMA_LISP" = "clisp" ]; then
>>> LC_ALL=C
>>> export LC_ALL
>>> if [ "$layout_autotools" = "true" ]; then
>>
>> I dunno -- if the user has set LC_ALL for themselves already,
>> this will clobber their setting, right?
>
> Of course it is intended to clobber the user's LC_ALL settings, because
> otherwise, with my settings, maxima with clisp crashes.
Well, is LC_ALL unset, or is it set to something?
If it is set, to what is it set?
Since LC_ALL is part of the locale stuff, I'm inclined to avoid
clobbering it, because presumably a user sets LC_ALL in order
to get some locale-specific behavior from programs which honor
locale settings.
> Of course maxima compiled with cmucl or sbcl doesn't have this problem.
That suggests to me that there is a bug or at least an idiosyncrasy
in Clisp. The locale stuff is pretty well defined, isn't it? Is it OK for
programs to interpret those settings in different ways? Specifically
in reference to your setting or non-setting of LC_ALL, how are
programs supposed to respond to that?
>> Can you run clisp by itself? If not, that suggests to me that the
>> problem is in the user's environment & not in Maxima.
I;m still wondering about this.
best
Robert Dodier