Re: Disabling XS translation functions - please help

[Patrice Dumas]

On Fri, Oct 27, 2023 at 01:56:20PM +0100, Gavin Smith wrote:
> I was attempting to disable the XS translation functions in the XS parser,
> as I said in another email.  This would be necessary for the XS parser to
> function correctly, and should allow for isolating and disabling the other
> new texi2any code that is causing a slowdown.

I do not really get why disabling XS translations would be necessary to
disable the other codes. To me it is quite unrelated.

> However, I found even this seemingly simple task impossible with the
> hours I've spent on it. I thought that we would disable the call to
> complete_indices in parser.c, and do it in Parsetexi.pm:

In general, simply disabling an XS function in one place is not enough,
one need to disable all or nothing, as the XS data that is set up by XS
code is needed for the following XS code.

> Question: why are we rebuilding the tree in rebuild_document when
> it has already been built?

It is in order to bring to perl the changes that are only in XS.

> I consider texi2any to be in a semi-broken state at the moment, with
> the new code entangled with the program in a way that I am finding
> difficult to remove.  I may not have much more time to work on this in
> the coming days.

I think that it needs to be removed in an all or nothing way, because
the changes in XS are needed for later XS codes to have the correct data
setup.

-- 
Pat