I should have mentioned that it is declared, but obj can be one of many classes only some of which have setOrdinal:
On Nov 26, 2010, at 6:46 PM, banane wrote:
> declare the method in your header file. "-(void)setOrdinal;"
>
> On Fri, Nov 26, 2010 at 9:08 AM, Mikkel Eide Eriksen
> <mikkel.erik...@gmail.com> wrote:
> Hi all,
>
> I have the following bit in my code:
>
> if ([obj respondsToSelector:@selector(setOrdinal:)]) {
> [obj setOrdinal:value];
> }
>
> XCode gives a warning that obj may not respond to setOrdinal: which won't be
> a problem unless something is really screwy. But how do I get rid of the
> warning? Or do I just live with it?
>
> Regards,
> Mikkel
> _______________________________________________
>
> Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
>
> 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/banane%40gmail.com
>
> This email sent to ban...@gmail.com
>
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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 arch...@mail-archive.com
