The compiler doesn't know what class the object belongs to. You're
sending the message either to a variable of type id or the result of
a method that returned id.The id type can hold any class, so if
there are two identically named methods with different signatures
(BOOL return type vs. void, for instance), it doesn't have enough
information to pick the right signature.
That would make sense but it was complaining on
[NSApp reportException: x];
And some other class just has
-(BOOL)reportException:(NSException*)e;
So I did't get why this should be ambiguous because NSApp obviously
can't be of type id. Well turns out - it actually is. And now it all
makes sense again :)
I've just replaced [NSApp ..] with [[NSApplication
sharedApplication] ...]
Thanks guys!
cheers
--
Torsten
_______________________________________________
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 [EMAIL PROTECTED]
