> I have been unable to successfully compile a file that includes
> freetype.h because that file uses both 'generic' and 'internal' to
> name two fields of a struct. I find it odd that this problem is not
> showing up for many other people. I found only two posts on the web
> complaining about the same thing. One suggested solution is to use
> '#define ' to change the generic keyword, before including the
> header file, and then using 'undef' immediately after. But I'm
> worried that might cause problems to show up later.
Both the keywords `generic' and `internal' are *not* standard but
probably a MS extension (or whatever). The solution you are giving is
the right one IMHO.
Werner
_______________________________________________
Freetype mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype
