Re: loop efficiency & messages
Re: loop efficiency & messages
- Subject: Re: loop efficiency & messages
- From: Guy English <email@hidden>
- Date: Wed, 23 Mar 2005 14:24:21 -0500
On Wed, 23 Mar 2005 18:59:17 +0000, Thomas Davie <email@hidden> wrote:
> No, but I would bet my bottom dollar that methods like NSTableView's
> selectRow:byExtendingSelection: will have disappeared a couple of
> major versions down the line.
... for apps linking against the new target OS maybe, and versioned
frameworks will take care of it anyway. John is making the point that
if the docs say "getCount" will be called and you've shipped an app
with it then it'll keep getting called for as long as Apple can
possibly do so. Apple won't be "optmizing" away documented behavior.
They *may* swap the search order such that the raw accessor is favored
but that's about it. Bringing up the Carbon transition as an example
of Apple tossing out old code is a little extreme I think.
Now personally I find the getXXX style for simple accessors in
Objective-C foreign, and it's a sign of a programmer applying habits
from another language. Note that the getXXX is only popular because
C++ won't let you name a member and an accessor the same thing, hence
the work around. The issue with the naming conventions is that they
are often a sign that the programmer has brought more than just the
conventions to the cocoa environment. More important are pattern
breakers - like if accessors don't respect the memory management
conventions for example. Or init methods that aren't called init. It's
a sign the programmer is trying to do things his way instead of going
with the flow.
Guy
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden