• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: What are the limitations of Dot Syntax?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: What are the limitations of Dot Syntax?


  • Subject: Re: What are the limitations of Dot Syntax?
  • From: email@hidden
  • Date: Sat, 06 Dec 2008 15:02:11 -0500

Namaste!

I'm going to add my two cents here (despite being a noob).

I like the dot syntax.

Why?

(and before I go any further, I realize this is not a Windows forum, and also realize this is a very general set of statements and quite open to debate)

Because, in the Windows world at least, the "dot" allowed you to refer to *members* of an object.

What are members? They are attributes of the object. In programming simplicity, they are: properties or methods.

So, what's wrong with the "dot" syntax?  Nada in my book.

A "fuller" implementation of the dot syntax is more desireable in my book. From whence I came, it sure made code very much more readable and quicker to write.

That being said, I don't have an issue with the way things are, nor do I really care much how they evolve, provided the evolution is for the better.

The bottom line, as long as your code is readable, digestible, consistent, and clearly commented in tricky spots for those who come after you (and yourself later down the road too), it really doesn't matter, does it?

Peace, Love, and Light,

/s/ Jon C. Munson II

Quoting Charles Srstka <email@hidden>:

On Dec 5, 2008, at 10:06 PM, Bill Bumgarner wrote:

Not really. 'name' is still something that is an accessor type thing, regardless of whether it is derived or declared via @property()

"dot abuse" refers to expressions like:

foo.retain;
bar.lockFocusIfCanDraw;

That is, expressions where you aren't really asking the object to retrieve some value, but are more or less telling the object to do something and return a result.

And, yes, there are grey areas.

So would something which is clearly not a property, but still returns an object, such as:

myObj = mySet.anyObject;

or:

enumerator = myArray.objectEnumerator;

be considered kosher?

Charles
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden



_______________________________________________

Cocoa-dev mailing list (email@hidden)

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:
This email sent to email@hidden


References: 
 >What are the limitations of Dot Syntax? (From: Jerry Krinock <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: glenn andreas <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: Jerry Krinock <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: Chris Hanson <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: Jerry Krinock <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: Bill Bumgarner <email@hidden>)
 >Re: What are the limitations of Dot Syntax? (From: Charles Srstka <email@hidden>)

  • Prev by Date: Re: What are the limitations of Dot Syntax?
  • Next by Date: Re: JSON Framework
  • Previous by thread: Re: What are the limitations of Dot Syntax?
  • Next by thread: Re: What are the limitations of Dot Syntax?
  • Index(es):
    • Date
    • Thread