On 2013-03-25, Rupert Swarbrick <rswarbrick at gmail.com> wrote:
>> 1. make it an option to build maxima-index.lisp at build time, the
>> cost is minimal when doing it in lisp, and it is pretty painless to
>> write a function to dump the info hash;
>
> I *really* don't want to do this. Basically, the offsets we store would
> be bogus when using multiple implementations in the presence of
> unicode. It was wrong with the perl script and I'd rather not have it
> wrong here. I agree that it's easy - in fact the first patch on the
> branch does this!
Um, to the best of my knowledge, the current scheme does work correctly
with unicode data.
Dumping the index would be useful as a debugging feature.
>> 2. make a user-level function available to pull in more info files
>> than just those supplied in the installation;
>
> That seems like a sensible thing to do. Maybe something like this?
>
> register_info_file (path);
How about load_documentation. We don't register anything else but we do
load stuff. Also the fact that it's a Texinfo file is incidental.
>> 3. make it optional to use the perl script during the build process.
>
> Bleurgh. We should have one way to do it. Otherwise we'll have weird
> bugs with one build system and not with the other.
Agreed.
best
Robert Dodier