NOW, I get it. Thanks! Problem solved.
(I knew you guys were seeing something I wasn't, so I'm glad I
persisted - no pun* intended).
- Leon
*okay, intended
On Sep 17, 2009, at 9:49 , Quincey Morris wrote:
On Sep 17, 2009, at 09:21, Leon Starr wrote:
But if there is no @property/@dynamic for license in my Truck
subclass, (only in the Auto subclasss) I cannot access
thisTruck.license without getting a compiler error. Which makes
total sense to me since one NSManagedObject subclass (Truck) is not
inheriting from another (Auto) in objc. They each inherit from
NSObject.
Nuh uh.
If the Objective-C classes are "Auto" and "Truck" (which are maybe
the same names as your Core Data entities, although they don't
*have* to match), then Auto *must* be a subclass of NSManagedObject:
@interface Auto : NSManagedObject ...
and Truck *must* be a subclass of Auto:
@interface Truck : Auto ...
That's what Ben meant when he said "class inheritance still applies
normally". The whole point of the exercise is to make the Objective-
C inheritance chain *match* the entity inheritance chain.
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/leon_starr%40modelint.com
This email sent to leon_st...@modelint.com
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
