>>>#define ALL_POINTS (FT_UShort*)((FT_Byte*)(NULL) - 1);
>>
>>Clever! I'll commit this to VTK and we'll see tomorrow.
>
> Well, this silenced Visual Studio, but now another compiler on another
> machine is complaining:
>
> <http://www.cdash.org/CDash/viewBuildError.php?type=1&buildid=514717>
>
> "warning #2061-D: integer operation result is out of range"
>
> I think perhaps it would be better to change this code instead of
> being 'cleaver'. Perhaps instead we could use a struct that
> contains a bool and a pointer. The bool could indicate this special
> ALL_POINTS state.
Can you provide a patch? Or shall we ignore the whole issue, simply
accepting that some compilers emit a harmless warning?
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
