Re: GC In DB Library

[Helge Hess]

Hi Gerrit,

I don't understand your question completly. GCObject only is used to
find cycles, but it doesn't have anything to do with the weak-references
problem we discussed in the other thread.

The easiest (and most compatible) solution to the -dealloc notification
problem is to invent an EOCustomObject class like in EOF 4.x which all
DB objects must inherit from and which can provide all the logic we
discussed (instead of modifying NSObject).

BTW: The BoehmGC support in GDL already works with weak-references and a
notification scheme.

Greetings
  Helge

Gerrit Van Dyk wrote:
> 
> Hi,
> 
> I have changed some of my classes to inherit of GCObject. Everything worked
> like before and I still get a lot of errors. Is there any method that needs
> to be called on the GarbageCollect class to let the garbage collector do its
> work? I still get an object that was autoreleased from the uniquing tables.
> These tables should not contain a reference to the old object anymore as
> this object was released. The reference the uniquing tables return is
> invalid.
> 
> Gerrit
> 
> -------------------------------------------------------------------------
> This e-mail is intended only for the use of the individual or entity named
> above and may contain information that is confidential and privileged,
> proprietary to the company and protected by law. If you are not the intended
> recipient, you are hereby notified that any dissemination, distribution or
> copying of this e-mail is strictly prohibited. Opinions, conclusions and
> other information in this message that do not relate to the official
> business of our company shall be understood as neither given nor endorsed by
> it.
> 
> _______________________________________________
> Discuss-gnustep mailing list
> Discuss-gnustep@gnu.org
> http://mail.gnu.org/mailman/listinfo/discuss-gnustep

-- 
SKYRIX Software AG - http://www.skyrix.com
Web Application Technology for Enterprises