Re: Performance profiling of makeinfo

[Gavin Smith]

On Fri, Dec 26, 2014 at 8:27 PM, Patrice Dumas <address@hidden> wrote:
> So a secondary parser is used, which means that all what is done
> regarding indices/nodes/sections... is forgotten when going out of gdt,
> and in any case in gdt there should be no such Texinfo code, it is only
> for strings to be translated.  So, I think that a better course of
> action would be to have a way to define a parser setting only a subset
> of parser options, and defining differently some keys, instead of
> copying simply passing references as they are not supposed to be
> modified in the code in gdt.
>
> I could propose something in the next days.
>
> Also, I suppose we could use dclone or something else in any case.

Yes, please do try it if you can think of a faster way for this. Same
goes for checking types of characters in Paragraph.pm. A speed saving
of, say, 5%-10% would be quite noticeable when the total run time is
over minute.