Robert Dodier <robert.dodier at gmail.com> writes:
> On 2013-01-02, Volker van Nek <volkervannek at gmail.com> wrote:
>
>> I understand. So it's possible to explicitly load a package by
>> wrapping load in ibase:10. .
>>
>> (%i1) ibase:16$
>> (%i2) block([ibase:10.], load(stringproc))$
>> (%i3) ascii(7a);
>> (%o3) z
>>
>> So a fix could be to wrap the corresponding source functions which
>> perform loading in ibase:10. . Which are these and what is $ibase at
>> Lisp level ?
>
> The Lisp variable is *READ-BASE* (and the corresponding one for obase is
> *PRINT-BASE*). Looks like the function LOADFILE (src/suprv1.lisp circa
> line 229) loads Lisp files for Maxima (including autoloading).
Yeah, but my question is why we clobber *READ-BASE* when loading lisp
files. I genuinely can't think of any situation where I would want to do
that... Frankly, I'm struggling to think of a situation where I'd want
it when load()ing .mac files either.
Has anyone a use for this? Otherwise surely we should just bind
*read-base* and ibase to 10 in load().
Rupert
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 315 bytes
Desc: not available
URL: <http://www.math.utexas.edu/pipermail/maxima/attachments/20130102/fc9683fe/attachment.pgp>;