Actually here is a better design: at the point of discovery, set a flag in the FT_Face structure. That way, there is no interference between a non-zero error code and the opportunity for the caller to ignore the problem.
Graham -----Original Message----- From: Werner LEMBERG [mailto:[EMAIL PROTECTED] Sent: 04 December 2008 10:21 To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; freetype-devel@nongnu.org Subject: Re: [ft-devel] Force PMingLiU like font do HINTING > 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
