On 12/9/2017 8:55 AM, Nick Wellnhofer wrote: > On 08/12/2017 10:26, Daniel Veillard wrote: >> what do you really gain by this ? >> Things which were known portable cross many platforms now become >> unclear again. >> Trio might be deprecated, I would ask Daniel Stenberg first, so in copy, > > Most of all, I want to get rid of the Trio dependency. I'm aware that > this change could break some ancient platforms but I'm willing to help > with fixes in a timely manner. > > If you think the change is too dangerous then I can revert it. But at > one point, we should discuss how to handle compatibility with 20+ year > old platforms. >
My opinion is that old hardware deserves old software. There comes a point where even the compilers no longer support a target. > That said, Trio still seems to be supported. The latest release is 1.16 > from 2014: > > https://sourceforge.net/projects/ctrio/files/trio/ > > Upgrading our copy of the Trio code should fix some compiler warnings, > but personally I'd prefer not having to deal with third party code at all. The other option is to take over the trio project and keep it updated to serve this project. This way you control the dependent library code. -- Earnie _______________________________________________ xml mailing list, project page http://xmlsoft.org/ xml@gnome.org https://mail.gnome.org/mailman/listinfo/xml
