Although those macros does nothing *at the moment* and purely for the purpose of suppressing warnings, as I said at the beginning, they can become useful if one replaces them with a equivalent set of macros, or inlined routines, which spills out warning/diagnostics info... that would make better fonts overall, eventually.
I do like the idea of shortening the macros and removing the "OVERFLOW_" part. So I'll wait a bit before going in that direction. -------------------------------------------- On Wed, 7/6/17, Behdad Esfahbod <[email protected]> wrote: I also find all those changes a distraction that make the code look uglier for no gain. IMO warnings are just that: warnings. When they don't make sense, one should turn them off, not bend the code to go around them... But then again that's my personal opinion and how I maintain my code. :) _______________________________________________ Freetype-devel mailing list [email protected] https://lists.nongnu.org/mailman/listinfo/freetype-devel
