On Sat, Mar 07, 2026 at 10:53:00AM +0000, Gavin Smith wrote: > On Wed, Mar 04, 2026 at 03:41:41PM +0100, Patrice Dumas wrote: > > Something you did not describe, and, in my opinion, could be simplified > > is the possibility to have XS extensions loaded at different steps. > > It is relevant when the XS extensions have just been done, but in the > > long run, I think that we should only have two possibilities, pure Perl > > or all the XS extensions + Perl for the remaining. I think that the > > fine grained level of control permitted by the TEXINFO_XS_PARSER, > > TEXINFO_XS_STRUCTURE and TEXINFO_XS_CONVERT variables could be removed > > in the long-term. > > I agree with this. I think all three of these variables could be removed > as soon as it is convenient.
I will remove documentation about TEXINFO_XS_PARSER and TEXINFO_XS_STRUCTURE from the user-facing documentation and move it to README-hacking with a mention that it will be removed at some point. I think that it is a good thing to keep TEXINFO_XS_CONVERT documented and working for now, until we reach the point where we do not translate more converters to C. I will still add a mention that it is transient. -- Pat
