Re: [ft-devel] freetype compilation warnings

[Sean McBride]

On 12/20/09 6:20 PM, Werner LEMBERG said:

>>> Just getting rid of _debug_mem_dummy would cause a problem?  Is
>>> there another way to create a non-empty file?  How about a useless
>>> but harmless #include, like #include <string.h>?
>>
>> Ah, I haven't thought of that.  Sounds like a good idea.
>
>Well, after some thinking I now believe that this doesn't work: The
>preprocessor removes everything and we thus still have an empty file
>to compile.
>
>I've now replaced it with a `typedef'.

I've updated VTK with this change, we'll see how tonight's builds do.

>>> FTC_GNode_Compare() has 2 parameters:
>>>
>>>   FT_LOCAL( FT_Bool )
>>>   FTC_GNode_Compare( FTC_GNode   gnode,
>>>                      FTC_GQuery  gquery );
>>>
>>> but it's being cast to FTC_Node_CompareFunc which is 3 parameters:
>>>
>>>   typedef FT_Bool
>>>   (*FTC_Node_CompareFunc)( FTC_Node    node,
>>>                            FT_Pointer  key,
>>>                            FTC_Cache   cache );
>
>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?  I'll look into it.

--
____________________________________________________________
Sean McBride, B. Eng                 address@hidden
Rogue Research                        www.rogue-research.com
Mac Software Developer              Montréal, Québec, Canada