NYTimes Objective–C Style Guide
github.com
NYTimes Objective–C Style Guide
1–10 of 51 posts
Re: NYTimes Objective–C Style Guide
#2> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants.
I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
Re: NYTimes Objective–C Style Guide
#3> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants. I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
I've previously shared your opinion on this issue as well, but the first answer to this StackOverflow question shows one good reason why one should opt for having the asterisk touching the variable.
http://stackoverflow.com/questions/2452335/asterisk-sometime...
Re: NYTimes Objective–C Style Guide
#4> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants. I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
My take on this has always been the pointerness is semantically part of the type, but syntactically it belongs with the variable.
Therefore I annoy both parties by putting a space on either side to protest the fact that everyone is wrong.
Re: NYTimes Objective–C Style Guide
#5It's strange that NYT seems to be transitioning to a full blown tech company. Good strange though.
Re: NYTimes Objective–C Style Guide
#6Here's their blog post about it:
http://open.blogs.nytimes.com/2013/08/01/objectively-stylish...
Re: NYTimes Objective–C Style Guide
#7> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants. I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
It's pretty easy to convince yourself that "* with the type" is wrong when you see this:
int* a, b; // a is int* but b is int
Re: NYTimes Objective–C Style Guide
#8Why do so many style guides mandate spaces for indentation?
Re: NYTimes Objective–C Style Guide
#9> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants. I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
[deleted]
Re: NYTimes Objective–C Style Guide
#10> Asterisks indicating pointers belong with the variable, i.e. NSString text not NSString text or NSString * text, except in the case of global string constants. I know I have it wrong, but I always feel that the the variable is of type "pointer to type" so isnt it fairer to have the asterisk paired with the type denoting it is of the kind "pointer to type"?
C has a sort of declaration-by-example syntax. You're declaring that *someVar has type NSString. (IMHO, thinking of it this way also makes more complex declarations like function-pointer types, types with qualifiers, etc., easier to read.)