Re: faulty documentation?
Re: faulty documentation?
- Subject: Re: faulty documentation?
- From: Chuck Hill <email@hidden>
- Date: Wed, 17 Sep 2008 09:58:12 -0700
This is probably a relic of legacy documentation. Long, long ago in
a language far, far away from Java, EOCustomObject kept the values in
instance variables and EOGenericRecord kept them in a dictionary. I
don't know if anyone even uses EOCustomObject these days nor what it
does now.
On Sep 17, 2008, at 9:45 AM, Florijan Stamenkovic wrote:
Hi all,
If you check out the docs for EOCustomObject's takeValueForKey and
takeStoredValueForKey you will see that there is talk of storing the
value in instance variables (_key or key), but there is not talk
about storing values in a value dict, which is what most likely
happens in the end. Some debugging shows that indeed an EO has a
package wide variable called __dictionary, of the
_EOMutableKnownKeyDictionary type where values are stored. Nice.
Should not that be mentioned in the docs? I guess another entry
should be inserted before "make a call to
handleTakeValueForUnboundKey" that would say that if the key is a
valid property key for that EO, the value is stored in it's dict?
Why would this be left out?
F
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
--
Chuck Hill Senior Consultant / VP Development
Practical WebObjects - for developers who want to increase their
overall knowledge of WebObjects or who are trying to solve specific
problems.
http://www.global-village.net/products/practical_webobjects
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden