Core Data Confusion

[Scott Stevenson]

On Feb 2, 2007, at 2:05 PM, Marcus S. Zarra wrote:

> It is not a bad thing to be accessing the primitive values in this  
> situation.  I believe that warning was for external access to the  
> values.  e.g. object A should be calling -getValueForKey: instead  
> of -getPrimitiveValueForKey: on object B.  This ensures that object  
> B has complete control over what happens when that value is accessed.

What do you think about the fact that -primitiveValueForKey isn't  
wrapped in will/did accessValueForKey? That seems like it could cause  
some bizarre behavior.

    - Scott