On Thu, Oct 26, 2023 at 06:45:10PM +0100, Gavin Smith wrote: > > > For timing optimization, it seems to me that we should have only one > > target, the combination were everything is done in XS. To me there is > > little point in trying to optimize other combinations, because they are > > very unlikely to be used. The only other combination I can imagine to > > be used is the perl only combination triggered by TEXINFO_XS=omit that > > could be used to workaround a bug in the full XS combination at the cost > > of performance. > > What about the case of when an XS converter hasn't been written yet?
The perl data is always rebuilt for now, so perl converters will work as usual. As a side note, it is not clear to me for which converter the work needed to translate perl to XS/C is worth the speed increase (besides HTML). For Plaintext/Info there is already XS code for the critical code, we can decide to do more at any time now that the C/XS structure are ready to use, but the gains will probably be lower. For Texinfo XML, I think that it is not useful as it is probably not used much. For Docbook and LaTeX, I have no idea whether those converters are used by more than a few people, I would think that they are not actually used much either. -- Pat
