Re: texi2any C code still built even though XS modules were disabled

On Sat, Jan 17, 2026 at 08:41:08PM +0100, [email protected] wrote:
> On Sat, Jan 17, 2026 at 07:33:42PM +0000, Gavin Smith wrote:
> > The only other idea I have is that Texinfo::XSLoader could get the value
> > itself in its own BEGIN { } block.
> 
> Indeed, I did not realize that XSLoader depended on Texinfo::ModulePath.
> 
> If we do that we should probably remove the corresponding BEGIN blocks
> from texi2any and test_utils.pl, as they become useless.  That's
> probably the best to do.

I made another change, not to override any function if disable_XS.  This
is more consistent with Texinfo::XSLoader init that already checks disable_XS
and it is overall much simpler as now all the setting and getting of disable_XS
is done in Texinfo::XSLoader.

-- 
Pat