I don't know what the status of this feature in the last Xcode version, but
clang supports the unused attribute on obj-c ivar.
I have something like this to workaround this kind of warning:
#if __has_feature(attribute_objc_ivar_unused)
#define UNUSED_IVAR __attribute__((unused))
#else
#define UNUSED_IVAR
#endif
and then
@interface Foo {
int ivar UNUSED_IVAR;
}
@end
Le 4 févr. 2011 à 00:59, James Bucanek a écrit :
> Hamish Allan <mailto:[email protected]> wrote (Thursday, February 3, 2011 4:05
> PM -0000):
>
>> On 3 February 2011 22:46, James Bucanek <[email protected]> wrote:
>>
>>> I have numerous instance variables which are
>>> only used by categories.
>>
>> If you compile using -Xclang -fobjc-nonfragile-abi2, you can declare
>> instance variables in class extensions and kill two birds (improve
>> locality of reference, remove warnings) with one stone.
>
> I thought non-fragile instance variables required 64-bit Intel and/or 10.5.
>
> I still have to compile for 32-bit, PPC, and (occasionally) OS 10.4, so
> moving my instance variables into categories doesn't seem practical at this
> point in time.
>
>
>
> James Bucanek
> ____________________________________________________________________
> Author of Professional Xcode 3 ISBN: 9780470525227
> <http://www.proxcode3.com/>
> and Learn Objective-C for Java Developers ISBN: 9781430223696
> <http://objectivec4java.com/>
>
> _______________________________________________
> Do not post admin requests to the list. They will be ignored.
> Xcode-users mailing list ([email protected])
> Help/Unsubscribe/Update your Subscription:
> http://lists.apple.com/mailman/options/xcode-users/devlists%40shadowlab.org
>
> This email sent to [email protected]
-- Jean-Daniel
_______________________________________________
Cocoa-dev mailing list ([email protected])
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
