On Sun, Oct 06, 2024 at 07:16:21PM +0100, Gavin Smith wrote: > > If it's accepted as part of the Texinfo code base it is the responsibility > of the Texinfo developers to maintain it, fix reported bugs, keep it > working with other changes in the code etc., at least if we want to still > be able to release the code in a working state for general use.
I was not clear, but the scenario I had in mind was the case of a converter already maintained in Perl, and the C++ contributed converter does the same as the Perl converter, but faster. In that case, if the contributor does not maintain it anymore and we are not motivated to do it either, we can simply remove it as the only loss would be a less fast converter. > > > It is possible that texi2any could be rewritten in a different language > > > in the future but I don't know what that language is. The language might > > > not even have been invented yet. > > > > In any case, having already C code written as it is now would hopefully > > help people wanting to do something related to Texinfo in high level > > languages and speed up some parts of the processing with low level > > functions. > > Yes I understand the benefit of having both high-level and low-level > languages combined. Python was mentioned in another message in thread > and although this is a nicer language than Perl (from my perspective, as > someone who has never programmed in Python), I am led to believe that > it is even slower than Perl. I do a lot of python, and to me it is very similar to Perl. I find the Python syntax a bit more aestethic than Perl and sets usable as hash keys are nice, but overall to me both are very similar. I do not think that it is slower than Perl. > I was thinking in the future there may > be some other language that is both high-level (e.g., automatic > memory management) and fast enough. I am not sure that it is really possible... -- Pat
