They shouldn't - that's invalid. Every "label" is a component of
the method name - [myRect setWidth:10.0 height:15.0] is calling a
completely separate method from [myRect setWidth:10.0 somethingElse:
15.0].
Well that example is straight out of the manual:
<...>
This method name uses unlabeled arguments. Unlabeled arguments make
it difficult to determine the kind and purpose of a method’s
arguments. Instead, method names should include labels describing
each of their arguments...
Interesting - I wasn't aware that unlabeled arguments existed
(primarily because they're not used in Cocoa). I'd stay away from
them, as they're strictly less clear than named arguments, and will
probably confuse other programmers just as they did me._______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com