Re: Dream Controls: TDcInfoTree

Dean Hill wrote:

I would imagine that there are a number of memory leaks which are
probably from circular references. Is that correct?

I could accept some memory leaks, but what I can't accept in production
code is a ticking time bomb: The dcInfoTree overwrites memory. I have
spend hours to find a fix for that, but with all these _AddRef and
Release calls, mixing reference variable and interfaces, converting
interfaces to pointers anv vici versa,... No thanks.


--
Regards,

Andreas Hausladen
.

Relevant Pages

  • Re: interface programming
    ... I have auto garbage collector so I can freely do: ... Without worrying about memory leaks. ... there are two common patterns for interfaces: ... COM style - AddRef/Release used to manage object lifetime. ...
    (microsoft.public.vc.stl)
  • Re: ModelMaker 8 based C# Eco Modeler released
    ... > If circular references is the only reason why you went with C# first and not ... > Delphi, then that could have easily been solved by using interfaces as the ... The MDA Eco framework dictates the implementation code, ... Eco uses classes, not interfaces. ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Is garbage collection here yet?
    ... memory leaks ... Java does *not* have problems with circular references. ... Java does some bookkeeping of what objects hold references ...
    (comp.lang.tcl)
  • Re: Forward class references across units
    ... I think the dangers of circular references would nasty. ... exclude said references from inheritance, ... Some would argue that you could create interfaces in unit C, ...
    (borland.public.delphi.non-technical)
  • Re: Where is Free method in TInterfacedObject?
    ... using TInterfacedObject ... ... That's the nice thing about interfaces... ... (Just watch for circular references.) ...
    (borland.public.delphi.language.objectpascal)