On Sat, Oct 05, 2024 at 08:29:49AM -0700, Per Bothner wrote: > On 10/5/24 3:00 AM, Gavin Smith wrote: > > > This adds C++ code to the project!! This is very concerning. We > > already have a lot of languages in the Texinfo project: TeX, Perl, C, > > even JavaScript. I have no desire to understand or maintain C++ code > > in Texinfo as well. It is also a lot for any new contributors in > > the future to get up to speed with (as things are, there may never be > > any such new contributors). Can we please find some alternative > > for whatever this C++ code is used for? > > As you might suspect, my concern is the opposite: Too much C and Perl - and > not enough C++. > There is no doubt in my mind that C++ is a more suitable language for the > texinfo project > than C or Perl. Nobody should be writing large chunks of code in C - it is > dangerous. > > Luckily, C can be converted incrementally to C++: I did that for the DomTerm > backend.
And that is precisely what I DON'T want to happen. I am not willing to work on texi2any any more if parts of it start being written in C++. 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.
