Re: New language feature in Delphi: Static instantiation of classes

for once, interfaces are created somewhere and not just appear magically
yes, they cause object to be released (if such thing is supported), but then
it is more of the idea of garbage collector which is planned for next
release of BDS

"Charles McAllister" <charles@xxxxxxxxxxx> wrote in message
news:44d254c6$1@xxxxxxxxxxxxxxxxxxxxxxxxx
Serge Dosyukov (Dragon Soft) wrote:
if it is what was implied, then please do not do this
it will be a big effort to maintain such thing on the big projects and
understand when and what was created/destroyed...
I would understand garbage collector idea, but not such free fly like
described in the report


how would this obsfucate the code anymore than the use of interfaces?


.

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: interface programming
    ... ICar pGenericCar = carFactory.createCar; ... Without worrying about memory leaks. ... delete this heap object since C++ interfaces have no ctor or dtor? ... the garbage collector will work exactly yhe same as in C#. ...
    (microsoft.public.vc.language)
  • Re: New language feature in Delphi: Static instantiation of classes
    ... Charles McAllister wrote: ... how would this obsfucate the code anymore than the use of interfaces? ...
    (borland.public.delphi.non-technical)