Re: enough of accessors - how about private method naming conventions in the real world?
Re: enough of accessors - how about private method naming conventions in the real world?
- Subject: Re: enough of accessors - how about private method naming conventions in the real world?
- From: Nicholas Riley <email@hidden>
- Date: Wed, 7 Aug 2002 02:29:45 -0500
- Mail-followup-to: Georg Tuparev <email@hidden>, "Michael B. Johnson" <email@hidden>, email@hidden
On Wed, Aug 07, 2002 at 09:22:59AM +0200, Georg Tuparev wrote:
>
What I ended up is a shell script (kind of integrated with emacs) that
>
makes class dump and looks for overridden methods. At the moment the
>
script is very dumb and reports also methods from the public API and
>
methods that explicitly call super's implementation - so I really use
>
this before code frees, new Dev Tools release and if my programs start
>
behaving strangely. But one day (hopefully one_day <<
>
NSDistantFuture ;-) I will improve this script so that I can make it a
>
post-compile build phase....
I wonder if it would be hard to do this as part of compilation? You
could have a compiler warning something like 'method XYZ shadows
private method implemented in superclass NSABC', and a pragma to
disable it on a per-method basis if you really know what you're doing.
--
=Nicholas Riley <email@hidden> | <
http://www.uiuc.edu/ph/www/njriley>
Pablo Research Group, Department of Computer Science and
Medical Scholars Program, University of Illinois at Urbana-Champaign
_______________________________________________
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.