> FreeType can't normally 'emit warning messages' because it is a > library, not an app - it's up to the caller how to deal with > errors. A new, well documented, error code that the caller can > choose to ignore is the way to go, in my opinion.
Sounds good. However, which function should return it? Or shall we add a new API function? Werner _______________________________________________ Freetype-devel mailing list Freetype-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/freetype-devel