Re:Lazarus – A Delphi-compatible cross-platform IDE
by pjmlp on Thursday August 10, 2017 @05:30AM
(#14977977)
For those lacking CS background, reference counting is an GC algorithm.
The 5th chapter from "The Garbage Collection Handbook", http://gchandbook.org/, one of the most renowned books in the field, there are of course other equally renowned sources I can refer to.
Re:Lazarus – A Delphi-compatible cross-platform IDE
by zerr on Thursday August 10, 2017 @07:03AM
(#14978449)
Formality aside, it's about deterministic GC vs nondeterministic GC.
Re:Lazarus – A Delphi-compatible cross-platform IDE
by pjmlp on Thursday August 10, 2017 @07:25AM
(#14978560)
Reference counting isn't deterministic in the presence of large complex data structures.
You will know when memory gets deleted, but not how long it will take, nor how much stack space the destructors will require to run.
Enjoy Herb Sutter's "Leak-Freedom in C++... By Default." at CppCon 2016, where he explains how those issues affect C++ and goes on to implement a tracing GC.
Re:Lazarus – A Delphi-compatible cross-platform IDE
by TimJYoung on Friday August 11, 2017 @02:51PM
(#14992998)
You would never code the SomeMethod like that, you would use this instead:
var
LObj: IMyInterface;
begin
LObj := TMyClass.Create;
DoTheFoo(LObj);
LObj.Foo;
end;
Re:Lazarus – A Delphi-compatible cross-platform IDE
by klipt on Thursday August 10, 2017 @02:05AM
(#14976894)
Oh, in that case that's no better than C++'s shared_ptr.
I remember Delphi being fun back in the day and it still compiles way faster than C++, but C++ is evolving and maybe with modules even the compilation speed gap will disappear...
Re:Lazarus – A Delphi-compatible cross-platform IDE
by undreren on Thursday August 10, 2017 @02:54AM
(#14977105)
I actually feel that shared_ptr is a better fix, because that makes the memory handling consistently opt-in, instead of inconsistent.
Re:Lazarus – A Delphi-compatible cross-platform IDE
by MageSlayer on Thursday August 10, 2017 @05:19AM
(#14977920)
I highly doubt it's production code.
Nobody uses both objects(pointers) and interfaces simultaneously. It's a quick way to disaster.
In practice Delphi/FPC interfaces serve their purpose.
Example:
I work with Delphi in my day job.