The compiler only knows about methods declared somewhere or the
headers, and Core Data accessor methods are handled at runtime and
not declared anywhere. It's only a warning and not an error because
the compiler is smart enough to know that Objective C can do cool
stuff like that.
One solution is to use [managedObject valueForKey:@"memo"] and
[managedObject setValue:@"test123" forKey:@"memo"] instead of the
accessors.
Malcolm is right. The dynamic properties are much much more
efficient than KVC (which is, as its name implies, by *key* i.e.
string based lookups, not native ObjC methods)
Use @interface to suppress the compiler warnings.
The dynamic properties are also more efficient than adding your own
KVC accessor methods, so don't add accessor methods that perform the
default behavior. Use custom accessor methods for adding custom
logic.
--
-Ben
_______________________________________________
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 [EMAIL PROTECTED]
