Re: Private, Protected methods in Obj C?
Re: Private, Protected methods in Obj C?
- Subject: Re: Private, Protected methods in Obj C?
- From: Jonathan Wight <email@hidden>
- Date: Wed, 03 Apr 2002 17:39:30 -0600
On 04/03/2002 16:14, "Ondra Cada" <email@hidden> wrote:
>
I guess twice nope. A *private* method -- or what I understand a private
>
method is -- is really nothing but a static function, in C++ with a
>
convenient access to properties. NOTHING MORE (or is it?). Since no
>
dynamic loveliness is *POSSIBLE BY DEFINITION* with a private method, why
>
should we care in the implementation?
The main usefulness you'd be cutting yourself off from is the ability to
pass the method around as a selector. I usually put my delegate/notification
methods in their own private category (or at least have been doing that
recently).
>
Don't take me wrong: I *DO* advocate using the dynamic runtime whenever
>
appropriate, for all those reasons of stability, flexibility, robustness,
>
upgradability, and you-name-it. But so far as I understand, privateness
>
means a very categorical "I don't want any of that!".
Well then we're essentially arguing the same thing - I was just pointing out
what I though to be bad advice.
Jon.
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.