On Jan 25, 2016, at 5:52 PM, Greg Parker <gpar...@apple.com> wrote:

> 
>> On Jan 24, 2016, at 3:55 PM, Graham Cox <graham....@bigpond.com> wrote:
>> 
>> In Objective-C 2, data members can be moved into a @interface MyClass () 
>> section which lives in the .m file, rather than in the header file as in the 
>> classic case. This makes sense - those data members are typically part of 
>> the private implementation details of a class and not part of the public 
>> interface. 
> 
> Even better, you can move them to @implementation itself. No need for the 
> extra class extension if everything is used inside a single file.
> 
> 
>> But is it worth updating older code to follow this convention? I’ve updated 
>> a lot of older code to declare @properties instead of classic getters and 
>> setters, and that definitely improves readability. This is a further step 
>> I’m contemplating but the benefits are less clear. Do you generally think 
>> this is worth doing?
> 
> A performance gain. @public and @protected ivars each create an exported 
> symbol; @private and @package ivars do not. Reducing symbol exports can 
> improve launch time and stripped executable size. Ivars declared in 
> @implementation or a class extension @interface are @private by default. 
> Ivars in the primary @interface are @protected by default. Therefore you 
> should either move your ivars out of the primary @interface, or leave them in 
> @interface but explicitly declare them @private or @package.

Wow.  This is awesome.  

It also leads directly to the question I had previously, “what are the proper 
naming conventions for these?”

Since a lot of Cocoa relies on visually identifying if the word in question 
starts with a capital letter, a lowercase letter or an _ to communicate to the 
programmer the exact nature of the thing they are looking at, what are the 
proper conventions for these?

Yeah, the ivar for an @property called myThing is _myThing and we can know that 
by looking at it with our eyeballs.  How do we extend that type of visual 
exposure of information of the “thing” being inspected in a similar manner?

Do we have any standards for this?  

If not, should we create some?

Thanks.
_______________________________________________

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to