On Wed, Oct 1, 2008 at 8:08 AM, Karan, Cem (Civ, ARL/CISD)
<email@hidden> wrote:
> I get the following messages:
>
> warning:passing argument <some number> of 'objc_setProperty' with different width due to prototype
> warning:passing argument <some number> of 'objc_setProperty' as signed due to prototype
> warning:passing argument <some number> of 'objc_getProperty' with different width due to prototype
> warning:passing argument <some number> of 'objc_getProperty' as signed due to prototype
>
> and these are repeated in no particular order many, many times. The only thing that changes is the argument number. But, changing all of this to Objective-C++ makes these warnings go away, so I'm guessing that there is some black magic that needs to be invoked for all time, or things go badly wrong, and that is what I'm running into.
It would be helpful to get the exact argument indexes you are seeing
in you warning messages.
As a guess I would say that the trailing boolean parameters that
objc_setProperty and the one that objc_getProperty has... however not
sure why you would be seeing this issue. May be interesting to look at
the preprocessed source and disassembly when you switch one of your .m
between Objective-C and Objective-C++ compiler.
It sounds like the normal Objective-C "BOOL" (signed char) is getting
changed to an unsigned of some other width.
-Shawn
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Objc-language mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
