Re: multiple inheritance equivalent in Core Data?
Re: multiple inheritance equivalent in Core Data?
- Subject: Re: multiple inheritance equivalent in Core Data?
- From: John Timmer <email@hidden>
- Date: Mon, 09 May 2005 15:26:08 -0400
> The overhead of adding what are effectively unused attributes to a
> model should not exactly over-tax the system, however I'm not sure in
> what sense you're wanting to "simplify the object graph"? What
> problem is there with adding the attributes to just those entities
> that need them?
The original issue is that I was adding three keys to the base class, when
most of the subclasses only needed to use two of them. The problem was that
it is a different two in most of the subclasses - there was no way to design
a tree to give the right keys to all the appropriate subclasses. Multiple
inheritance would have allowed finer grained control over which subclasses
got what keys, but it's not an ObjC option.
I figured having extra keys wasn't a waste (and posts here, including yours,
indicate it's not), so I did put them in the base class. I was just
wondering whether there was some other way of solving it.
Thanks,
JT
_______________________________________________
This mind intentionally left blank
_______________________________________________
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