Re: Xcode / Interface Builder creates nil binding of an NSTextField instance ...
Re: Xcode / Interface Builder creates nil binding of an NSTextField instance ...
- Subject: Re: Xcode / Interface Builder creates nil binding of an NSTextField instance ...
- From: Chris Hanson <email@hidden>
- Date: Sun, 20 Jun 2010 01:37:14 -0700
On Jun 19, 2010, at 7:21 PM, Jay Reynolds Freeman wrote:
> On Jun 19, 2010, at 5:20 PM, Jens Alfke wrote:
>
>> On Jun 19, 2010, at 4:15 PM, Jay Reynolds Freeman wrote:
>>
>>> IBOutlet NSTextField *ExpectStuff;
>>
>> Not directly relevant, but as a matter of Obj-C coding style,
>> instance variables should not be capitalized.
>
> That's why they call it "style" ... :-)
Not only will other developers have an easier time working with your code if it follows the documented conventions, but so will Cocoa itself. Many Cocoa’s more dynamic features — such as Key-Value Coding and Key-Value Observing — depend significantly on your code following the documented Cocoa conventions.
For one example, if you have a property “foo” and want to follow Smalltalk getter and setter conventions — which would mean naming its getter method -foo and its setter method -foo: — KVC will not know that “foo:” is its setter.
So when dealing with Cocoa, it’s more than just a matter of style.
— Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden