Skip navigation.
 
mlRe: warning: 'NSEntityDescription' may not respond to
FROM : mmalc crawford
DATE : Fri May 30 20:51:50 2008

On May 30, 2008, at 3:09 AM, Peter Burtis wrote:

> 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.
>

No, don't do this.
If you don't want to define a custom managed object class, the correct 
solution is to add a category of NSManagedObject that defines the 
methods to keep the compiler happy.
<http://developer.apple.com/documentation/Cocoa/Conceptual/CoreData/Articles/cdAccessorMethods.html#//apple_ref/doc/uid/TP40002154-SW9
>
Substituting KVC methods just to suppress compiler warnings needlessly 
makes your application less efficient.

mmalc

Related mailsAuthorDate
mlwarning: 'NSEntityDescription' may not respond to Steven Hamilton May 30, 11:17
mlRe: warning: 'NSEntityDescription' may not respond to Peter Burtis May 30, 12:09
mlRe: warning: 'NSEntityDescription' may not respond to Kyle Sluder May 30, 15:35
mlRe: warning: 'NSEntityDescription' may not respond to Fritz Anderson May 30, 20:16
mlRe: warning: 'NSEntityDescription' may not respond to mmalc crawford May 30, 20:51
mlRe: warning: 'NSEntityDescription' may not respond to Steven Hamilton May 30, 23:40
mlRe: warning: 'NSEntityDescription' may not respond to Ben Trumbull May 30, 23:49
mlRe: warning: 'NSEntityDescription' may not respond to Chris Hanson May 31, 10:13