2014/10/15 下午 10:08:23

iphone Programming Glossary: entrant

NSManagedObjectContext performBlockAndWait: doesn't execute on background thread?

http://stackoverflow.com/questions/11831946/nsmanagedobjectcontext-performblockandwait-doesnt-execute-on-background-thread

calling thread. This is documented and reasserted in several WWDC presentations . Furthermore performBockAndWait is re entrant so nested calls all happen right in that calling thread. The Core Data engineers have been very clear that the actual thread.. Furthermore you can see the unspoken implications of this in that the way in which performBlockAndWait provides re entrant support breaks the FIFO ordering of blocks. As an example... context performBlockAndWait ^ NSLog @ One context performBlock.. version. In general avoid sync versions whenever possible because dispatch_sync can cause a deadlock and any re entrant version like performBlockAndWait will have to make some bad decision to support it... like having sync versions jump the..

Is calling -[NSRunLoop runUntilDate:] a good idea?

http://stackoverflow.com/questions/4923621/is-calling-nsrunloop-rununtildate-a-good-idea

any method that could be called by the run loop you are invoking unless the overlapping call tree is completely re entrant. The Cocoa Touch UI code is not documented as re entrant in fact there are warnings hints from Apple DTS that it is not.. invoking unless the overlapping call tree is completely re entrant. The Cocoa Touch UI code is not documented as re entrant in fact there are warnings hints from Apple DTS that it is not so if your fetch data handler can in any way be called by.. from Apple DTS that it is not so if your fetch data handler can in any way be called by a UI method or other non reentrant code that could be called in the UI run loop calling the UI run loop from inside it is not recommended. share improve this..