Dear Werner, On Fri, 13 Oct 2006 00:00:10 +0200 (CEST) Werner LEMBERG <[EMAIL PROTECTED]> wrote: >> So, I wish if I could forbid (or disturb) the functions in building >> phase of the problematic application. Of course, keeping the function >> available for runtime linker is important (to avoid users from >> "unresolved symbol" trouble). There's any standard method to issue >> an error in cc1, with meaningful informative message? > >What about > > __attribute__ ((deprecated)) > >(see gcc.info, section `Declaring Attributes of Functions')?
Thank you very much, I was not aware of the method by __attribute__(()). MacOSX's native compiler is gcc, and it is very elegant solution. But, it seems that deprecated attribute cannot interrupt the compiling procedure, just issues warning (and it can be switched off). I think it's insufficient, because often too many warnings are printed within building procedure of problematic softwares, I wish method to interrupt the building. I'm thinking of following to Turner's propose, how do you think of the introduction of ugly hack into ftmac.h? Regards, mpsuzuki _______________________________________________ Freetype-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/freetype-devel
