On Jun 5, 2008, at 10:26 PM, Graham Cox wrote:
I guess the question is, given an object type 'id', which method
signature will the compiler go with? Does the return type affect the
method signature? (In C++ it doesn't for example), so two methods:
- (CGPoint) position;
- (float) position;
might well have identical signatures. The compiler doesn't have an
object type to narrow it down, so which will it use - the first it
finds maybe.
You might want to experiment with enabling one or more of the
following optional warnings:
-Wselector
Warn if multiple methods of different types for the same selector are
found during compilation. The check is performed on the list of
methods in the final stage of compilation. Additionally, a check is
performed for each selector appearing in a "@selector(...)"
expression, and a corresponding method for that selector has been
found during compilation. Because these checks scan the method table
only at the end of compilation, these warnings are not produced if the
final stage of compilation is not reached, for example because an
error is found during compilation, or because the -fsyntax-only option
is being used.
-Wstrict-selector-match
Warn if multiple methods with differing argument and/or return types
are found for a given selector when attempting to send a message using
this selector to a receiver of type "id" or "Class". When this flag is
off (which is the default behavior), the compiler will omit such
warnings if any differences found are confined to types which share
the same size and alignment.
-Wundeclared-selector
Warn if a "@selector(...)" expression referring to an undeclared
selector is found. A selector is considered undeclared if no method
with that name has been declared before the "@selector(...)"
expression, either explicitly in an @interface or @protocol
declaration, or implicitly in an @implementation section. This option
always performs its checks as soon as a "@selector(...)" expression is
found, while -Wselector only performs its checks in the final stage of
compilation. This also enforces the coding style convention that
methods and selectors must be declared before being used.
j o a r
_______________________________________________
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]
