Re: Implementation across several files
Re: Implementation across several files
- Subject: Re: Implementation across several files
- From: Ondra Cada <email@hidden>
- Date: Thu, 20 Apr 2006 22:41:57 +0200
Jonathon,
On 20.4.2006, at 15:13, Jonathon Mah wrote:
(Matter of fact, I would advocate to change the runtime to base
*all* instances on a dictionary /more precisely, a special
hashtable/, which would vastly improve the flexibility, allow for
much better interface/implementation separation, and also remove
the one fragility ObjC has, but that is definitely beside the
point at this moment :))
Yes, let's move instance variable declarations out of the header
while we're at it. Headers should contain what other users need to
know about a class, and no more!
Definitely. That would be one of the many advantages :)
Ondra, you have given me an idea: Could you get the effect of this
with some neat coding? Instance variable names are available in the
compiled app -- for example, class-dump shows them, and KVC uses
them IIRC -- so you could write a macro or something to do dynamic
lookup. Then use an extra dictionary to hold extra ivars not
declared at compile-time.
Again, definitely: far as you use accessors consistently, there even
is no need for too smart coding. Would be nice though to have some
compiler support (but even that could be, I guess, added by smart
preprocessing).
---
Ondra Čada
OCSoftware: email@hidden http://www.ocs.cz
private email@hidden http://www.ocs.cz/oc
_______________________________________________
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