Re: Property name clashes with a method implemented by NSManagesObject or NSObject
Re: Property name clashes with a method implemented by NSManagesObject or NSObject
- Subject: Re: Property name clashes with a method implemented by NSManagesObject or NSObject
- From: Francis Derive <email@hidden>
- Date: Mon, 6 Feb 2006 07:23:29 +0100
mmalc,
As your indication :
"Although the description method does not cause a fault to fire, if
you implement a custom description method that accesses the object’s
persistent properties, this will cause a fault to fire. You are
strongly discouraged from overriding description in this way."
Merci.
Francis.
On Feb 5, 2006, at 12:50 AM, mmalcolm crawford wrote:
On Feb 3, 2006, at 4:18 AM, Francis Derive wrote:
The first property of my entity is "name" - no claim -, but the
second property "description" raises the above subject alert panel.
I wonder why there is so much to be strict as I would believe the
method name "description" will be clearly related to the class
associated to the entity - and no other existing class.
However, I would believe the method "name" would be candidate to
the same alert.
Per the alert panel, 'description' is an existing method of
NSObject, 'name' is not. 'description' also has other issues -- see
<http://developer.apple.com/documentation/Cocoa/Reference/
CoreData_ObjC/Classes/NSManagedObject_index.html>.
mmalc
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40mac.com
This email sent to email@hidden
_______________________________________________
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