Comments on: Objective-C 2.0 http://importantshock.wordpress.com/2006/12/27/objective-c-20/ Tue, 27 Jan 2009 20:02:03 +0000 http://wordpress.com/ hourly 1 By: Jon H http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-31 Jon H Tue, 02 Jan 2007 00:21:46 +0000 http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-31 @private/@protected/@public go back to the early 1990's, at least as far as being applicable to instance variables. I found them mentioned in a 1993 usenet thread in comp.sys.next.programmer. @private/@protected/@public go back to the early 1990’s, at least as far as being applicable to instance variables.

I found them mentioned in a 1993 usenet thread in comp.sys.next.programmer.

]]> By: Mike Abdullah http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-27 Mike Abdullah Wed, 27 Dec 2006 23:41:22 +0000 http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-27 Not wanting to upset, but I feel I ought to point out that the @private etc. directives are already in 10.4. In fact I think they've been around since Panther and earlier. I'm waiting to see what happens with the whole properties business. Not wanting to upset, but I feel I ought to point out that the @private etc. directives are already in 10.4. In fact I think they’ve been around since Panther and earlier.

I’m waiting to see what happens with the whole properties business.

]]> By: Scott Stevenson http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-25 Scott Stevenson Wed, 27 Dec 2006 22:31:31 +0000 http://importantshock.wordpress.com/2006/12/27/objective-c-20/#comment-25 There's a good reason for the access control stuff, though I'm not sure it's public yet. As for properties, there are some minor drawbacks, but I don't think it's realistic to hold onto a C-centric view of the world until the end of time. The best thing Apple can do is maintain the important parts of the Objective-C runtime, and meet somewhere in the middle on syntax. Frankly, between door number one: value = [[[[object this] that] something] somethingElse] ... and door number two: value = object.this.that.something.somethingElse I'll take door number two. There’s a good reason for the access control stuff, though I’m not sure it’s public yet.

As for properties, there are some minor drawbacks, but I don’t think it’s realistic to hold onto a C-centric view of the world until the end of time. The best thing Apple can do is maintain the important parts of the Objective-C runtime, and meet somewhere in the middle on syntax.

Frankly, between door number one:

value = [[[[object this] that] something] somethingElse]

… and door number two:

value = object.this.that.something.somethingElse

I’ll take door number two.

]]>