Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I was just wondering if there is any need besides backwards compatibility to keep the @private keyword in objective-c, since class extensions provide a much better way to declare your private iVars. Are there any other reasons for keeping the @private directive?.
The 32-bit x86 architecture still requires declaring ivars in the primary
@interfaceblock. The ability to synthesize ivars (via properties or class extensions or on the@implementation) is only available for 64-bit x86 and ARM architectures (and, presumably, any future architecture as well).