Thread overview
[Issue 18613] Documentation: recommended construction/destruction patterns for manual memory management
Mar 15, 2018
greenify
Mar 15, 2018
Manu
Dec 17, 2022
Iain Buclaw
March 15, 2018
https://issues.dlang.org/show_bug.cgi?id=18613

greenify <greeenify@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |greeenify@gmail.com

--- Comment #1 from greenify <greeenify@gmail.com> ---
Thanks a lot for opening the request on his behalf.
(We might modernize Bugzilla, so stay tuned)

Does your colleague know about the GC series?https://dlang.org/blog/the-gc-series

Also did your colleague find https://dlang.org/articles/cpptod.html?

Maybe this page could then be expanded.

> Current solution, make a function myDelete that calls dtor and free by hand.

The preferred way is to use make and dispose from std.experimental.allocator - they are the D analogies to malloc and free though a lot smarter (and dispose calls the destructor).

--
March 15, 2018
https://issues.dlang.org/show_bug.cgi?id=18613

--- Comment #2 from Manu <turkeyman@gmail.com> ---
He's interacting with existing C++ code, and doesn't want to have conflicting allocation strategies. It's gamedev, so custom allocation mechanisms are already in use.

He did find the cpptod, read it, but he suggested there were still questions. I'll dig for his thoughts at lunch tomorrow :)

I'll point him to std.experimental.allocator.

Thanks!

--
December 17, 2022
https://issues.dlang.org/show_bug.cgi?id=18613

Iain Buclaw <ibuclaw@gdcproject.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|P1                          |P4

--