Le lun. 29 déc. 2025, à 11 h 05, Robin Watts via Tiff <[email protected]> a écrit :
> On 29/12/2025 11:08, Roger Leigh via Tiff wrote: > > I mentioned this as a possibility during discussion > > in mid December, > > Please be aware that moving libtiff to C++ instead of C would cause > problems for various pieces of software that depend upon it. > > The most obvious case, from my point of view, is Ghostscript. > > We are careful to avoid any compulsory dependencies that depend upon > C++, as we have to run on lots of systems where C++ presents a problem. > I agree with this point. I find the proposal's categorization of "let's build this as C++" as low risk bordering on ridiculous. It will break stuff on some platforms, that's for certain. The rest of it looks more or less like "let's rewrite everything". > Now, I imagine that some people will argue that losing support for such > "legacy" code is just too bad. So be it, but be aware that this means > the old version of the lib will likely live on as a source of security > bugs for years to come. That's the discussion we need to have before any of the more technical aspects of this. There's no way we can move core libtiff to modern C++ as proposed and retain the wide support libtiff provides. I think even older C++ would be a stretch. There also needs to be a discussion about the value of doing this. What does it bring that we can't have without it? It will also bring new bugs. Do the improvements outweigh the problems? Is this true at every point along the way or only 5-10 years from now? Olivier
_______________________________________________ Tiff mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/tiff
