• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
When exactly does a fault get fired?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

When exactly does a fault get fired?


  • Subject: When exactly does a fault get fired?
  • From: email@hidden
  • Date: Fri, 17 Feb 2006 00:51:30 -0800

Hi, list, I've got a question concerning faults in core data.
If an entity has a attribute that is in the data model and has an accessor for it, when a call to the accessor occurs, does the fault fire exactly when the call [object valueForKey:@"Key"] gets sent, or, in the custom method, does the fault stay un-fired until I call [self willAccessValueForKey:@"Key"] or [self primitiveValueForKey:@""]....


I'm asking because I would like to cache a value without doing a separate accessor, so I'm wondering if I can return the cache if it exists instead...without fire a fault (thats the reason why I want to use a cache)....


Thanks in advance!

Andre
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


  • Follow-Ups:
    • Re: When exactly does a fault get fired?
      • From: mmalcolm crawford <email@hidden>
    • Re: When exactly does a fault get fired?
      • From: AurĂ©lien HugelĂ© <email@hidden>
  • Prev by Date: Re: How to load a special nib file in cocoa?
  • Next by Date: Re: When exactly does a fault get fired?
  • Previous by thread: Bindings - duplicate entries in NSPopupButton
  • Next by thread: Re: When exactly does a fault get fired?
  • Index(es):
    • Date
    • Thread