[hoc-devel] Issue 11 in hoc: Do not completely override retain/release

[<cod...@go...>]

Status: Started
Owner: james.c...@usma.edu
Labels: Type-Enhancement Priority-Medium Usability

New issue 11 by james.c...@usma.edu: Do not completely override  
retain/release
http://code.google.com/p/hoc/issues/detail?id=11

NSManagedObject does some kind of magic with its retain/release which  
breaks when HOC
overrides them. (The NSManagedObject documentation also specifically states  
that those methods
"must not" be overridden).  Unfortunately this is a relatively difficult  
thing to create a test case for,
but "in the wild" what happens is the object gets prematurely deallocated,  
usually upon the first
edit to a managed object after loading from a persistent store.

I have a patch at home that fixes the problem by changing the behavior of  
HOC's retain/release
implementations to use calls to [super retain], [super release], and [super  
retainCount], however I
don't know whether this would be considered an unnecessary performance hit  
to do so in all
cases.  Should I push the change or just post a patch here for review?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings