>>Yes, this seems to be the cause. However, fixing this is not easy
>>(except providing a new macro which is rather unelegant) -- at least
>>for me. Any idea how to work around the warning?
>
> Not off the top of my head. The other question is: how serious is
> this warning?
Good question. Up to now it's the only compiler which warns and,
AFAIK, no bugs have been reported with this part of the cache code.
> I'll look into it.
Thanks.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
