[Issue 2858] D specs allow GC implementations that don't call finalizers

https://issues.dlang.org/show_bug.cgi?id=2858 Andrei Alexandrescu and...@erdani.com changed: What|Removed |Added Version|D1 D2 |D2 --

[Issue 2858] D specs allow GC implementations that don't call finalizers

https://issues.dlang.org/show_bug.cgi?id=2858 Walter Bright bugzi...@digitalmars.com changed: What|Removed |Added Hardware|x86 |All --

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #8 from s...@iname.com 2009-04-20 04:28 --- (In reply to comment #7) (In reply to comment #3) SDWF tries to get around this by running a collection if creation of a GDI object fails, in case it frees some system

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 s...@iname.com changed: What|Removed |Added CC||s...@iname.com

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 fa...@gmx.ch changed: What|Removed |Added CC||fa...@gmx.ch --- Comment #2 from

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #3 from s...@iname.com 2009-04-19 18:31 --- (In reply to comment #2) I agree that making the finalizers more deterministic is a good idea. As discussed in the NG I see two problems: 1) the use of finalizers for any

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #4 from llu...@gmail.com 2009-04-19 18:41 --- (In reply to comment #1) To fix this, several paths can be taken: 1) Guarantee finalization, at least at program end 2) Remove finalizers completely from the collection

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #5 from s...@iname.com 2009-04-19 19:10 --- (In reply to comment #4) Perhaps better: The garbage collector runs the destructor for all unreferenced objects before freeing their memory. At program exit the memory

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #6 from llu...@gmail.com 2009-04-19 20:02 --- (In reply to comment #2) I agree that making the finalizers more deterministic is a good idea. As discussed in the NG I see two problems: 1) the use of finalizers for any

[Issue 2858] D specs allow GC implementations that don't call finalizers

http://d.puremagic.com/issues/show_bug.cgi?id=2858 --- Comment #7 from llu...@gmail.com 2009-04-19 20:07 --- (In reply to comment #3) SDWF tries to get around this by running a collection if creation of a GDI object fails, in case it frees some system resources in order to try