Actually it doesn't emit a warning.
If you recall my problem a few weeks ago with:
- (float) position;
vs.
- (int) position;
the compiler sailed blithely on without a mention, generating code
that smashed the stack to pieces.
This is different from the situation that does emit a warning, where
the method is completely unknown and is assumed to return type 'id'. I
do compile with many additional warnings, but I haven't found one that
picks up this problem.
Graham
On 11 Jul 2008, at 1:40 am, Jens Alfke wrote:
If it finds more than one method, and the return types differ, then
the situation is ambiguous … so it emits a warning
_______________________________________________
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]
