[Issue 4104] No way to get notified about D runtime termination.
https://issues.dlang.org/show_bug.cgi?id=4104 Max Samukha changed: What|Removed |Added CC||maxsamu...@gmail.com --- Comment #4 from Max Samukha --- QtD is dead. This can be closed if nobody else needs it. --
[Issue 4104] No way to get notified about D runtime termination.
https://issues.dlang.org/show_bug.cgi?id=4104 Vladimir Panteleev changed: What|Removed |Added Hardware|Other |All OS|Linux |All --- Comment #3 from Vladimir Panteleev --- If this enhancement request is still actual today, please submit the patch as a pull request; otherwise, it's unlikely anything will be done about it. I'll leave this open because it doesn't seem too unlikely that another project will require a similar addition, in which case having an existing issue could be useful. --
[Issue 4104] No way to get notified about D runtime termination.
https://issues.dlang.org/show_bug.cgi?id=4104 Vladimir Panteleev changed: What|Removed |Added Keywords||patch --
[Issue 4104] No way to get notified about D runtime termination.
http://d.puremagic.com/issues/show_bug.cgi?id=4104 Sean Kelly changed: What|Removed |Added Status|NEW |ASSIGNED --- Comment #1 from Sean Kelly 2010-07-20 15:09:44 PDT --- Is this something that can be addressed via a shared module dtor, or is that too early/late in the termination process? isHalting seems of limited utility so I tentatively deprecated it, but perhaps it should be replaced by a status field instead? -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
[Issue 4104] No way to get notified about D runtime termination.
http://d.puremagic.com/issues/show_bug.cgi?id=4104 --- Comment #2 from Max Samukha 2010-07-22 01:21:54 PDT --- I am afraid it is too early. The problem is that during the final GC cycle wrappers owned by D (subject to garbage collection) will be destroyed. As part of their destruction process, they will destroy their corresponding C++ objects, which may destroy other C++ objects, which will destroy their D wrappers (those added to roots). Though I am not entirely sure whether the last-mentioned wrappers need to be destroyed at program exit, I tend to think they do, just like the wrapper that owns them (that is the one that indirectly causes their destruction). >From the above follows that we need to know when the final GC cycle has been finished, so that QtD doesn't try to destroy wrappers for the C++ objects that survived that cycle. Obviously isHalting does not help here because it is set before the GC cycle is initiated. A field of an enum type indicating the current runtime state would be great. -- Configure issuemail: http://d.puremagic.com/issues/userprefs.cgi?tab=email --- You are receiving this mail because: ---
