>> ... the maintainer cannot introduce the change breaking the
>> backward compatibility ...
>
> Which is why I suggested a change that would *not* break backward
> incompatibility. Whatever code that might actually exist that checks
> for an error code can continue to do so.
It would be very useful if you could show us a practical example. For
example, HarfBuzz (which is admittedly C++) never calls `abort' or
`exit' within the library code...
Werner
_______________________________________________
Freetype mailing list
Freetype@nongnu.org
https://lists.nongnu.org/mailman/listinfo/freetype
