On 2005-10-07 17:41, Alastair Houghton said:
>I'm assuming that this is C++ code (or ObjC++ code)
It is.
>where this warning would come from otherwise, in which case a quick
>review of the GCC code reveals that there is indeed no way to disable
>this warning (short of changing the file gcc/cp/call.c, that is).
Cool, thanks for checking!
>It should be relatively easy to add an option to GCC to control this
>warning if you *really* need to disable it. Otherwise you could adopt
>the approach I saw a while back, which was to always run the compiler
>through a Perl script that filtered out unwanted warnings. (I can't
>say I'm a huge fan of that, but it might be a good option for you, which
>is why I mention it).
Or dear, that sounds worse than casting. :) After fixing some warnings
in header files, its down to mere hundreads, so I guess I'll bite the bullet.
Thanks a lot.
--
____________________________________________________________
Sean McBride, B. Eng email@hidden
Rogue Research www.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
