Re: Programming Style: Method Definition with or without a semicolon.
Re: Programming Style: Method Definition with or without a semicolon.
- Subject: Re: Programming Style: Method Definition with or without a semicolon.
- From: Marc Respass <email@hidden>
- Date: Thu, 15 Oct 2009 22:39:59 -0400
Ric
1) I've seen an alternative way of defining a method, with the
semicolon after the declaration, before the body:
- (NSArray *)sortedIncredients; <-- notice the semicolon
{
...
}
2) ... versus the standard declaration + body of the definition
(without the semicolon):
- (NSArray *)sortedIncredients {
...
}
Both seem to work the same.
Is there any benefit of (1) over (2) or is it merely style of
programming?
It is definitely a question of style. I prefer #1 above. I prefer to
have my brackets on the next line and by including a semi-colon at the
end, I can triple click my new method, copy, and paste it into the
header and it works since the semi-colon is required in the header.
Likewise, I can go to the header of a class, triple-click and copy a
method and just paste it into my implementation (delegate method or
override) and it's good. But other than copying and pasting, I can't
see any advantage (though it's easier for me to read but probably just
because that's what I'm used to).
Hope this helps
Marc
_______________________________________________
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
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden