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: Georg Tuparev <email@hidden>
- Date: Wed, 7 Aug 2002 09:51:11 +0200
On Wednesday, August 7, 2002, at 09:29 AM, Nicholas Riley wrote:
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.
Should be doable, though I do not know how hard (while I was
implementing my solution I reused some old sources I've written back at
NeXT times). One complication is that we actually do not know all loaded
bundles until they are loaded. At a runtime I am forcing my app to load
all bundles it is aware of. But there are third party bundles that my
app (and I) are not aware of ... oh well....
cheers
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
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.