digitalmars.D - Custom delete not getting called
- d coder <dlang.coder gmail.com> Jun 24 2011
- Ali =?iso-8859-1?q?=C7ehreli?= <acehreli yahoo.com> Jun 24 2011
- Jonathan M Davis <jmdavisProg gmx.com> Jun 25 2011
--000325559162a095f404a681440b Content-Type: text/plain; charset=ISO-8859-1 Hello People I was just trying out custom memory allocation/deallocation that can be found on the link http://www.d-programming-language.org/memory.html#newdelete The problem is that the delete function is never getting called. I have put an example test case at the end of the email. Any ideas? Regards - Puneet import core.memory : GC; import std.stdio; import std.exception; // enforce class Foo { string value = "."; new(size_t sz) { write("+"); void* p = enforce(GC.malloc(sz), "Out of memory while allocating Foo"); GC.addRange(p, sz); return p; } delete(void* p) { write("-"); if (p) { GC.removeRange(p); GC.free(p); } } } void main() { for (size_t i = 0; i < 32; ++i) { Foo foo = new Foo(); write(foo.value); } } --000325559162a095f404a681440b Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hello People<div><br></div><div>I was just trying out custom memory allocat= ion/deallocation that can be found on the link=A0<a href=3D"http://www.d-pr= ogramming-language.org/memory.html#newdelete">http://www.d-programming-lang= uage.org/memory.html#newdelete</a></div> <div><br></div><div>The problem is that the delete function is never gettin= g called. I have put an example test case at the end of the email.</div><di= v><br></div><div>Any ideas?</div><div><br></div><div>Regards</div><div> - Puneet</div><div><br></div><div><br></div><div><br></div><div><div>import= core.memory : GC;</div><div>import std.stdio;</div><div>import std.excepti= on;<span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span>// enf= orce</div> <div><br></div><div>class Foo {</div><div>=A0 string value =3D "."= ;;</div><div><br></div><div>=A0 new(size_t sz) {</div><div>=A0 =A0 write(&q= uot;+");</div><div>=A0 =A0 void* p =3D enforce(GC.malloc(sz),</div><di= v><span class=3D"Apple-tab-span" style=3D"white-space:pre"> </span> =A0 = =A0 =A0"Out of memory while allocating Foo");</div> <div>=A0 =A0 GC.addRange(p, sz);</div><div>=A0 =A0 return p;</div><div>=A0 = }</div><div><br></div><div>=A0 delete(void* p) {</div><div>=A0 =A0 write(&q= uot;-");</div><div>=A0 =A0 if (p) {</div><div>=A0 =A0 =A0 GC.removeRan= ge(p);</div><div>=A0 =A0 =A0 GC.free(p);</div> <div>=A0 =A0 }</div><div>=A0 }</div><div>}</div><div><br></div><div>void ma= in() {</div><div>=A0 for (size_t i =3D 0; i < 32; ++i) {</div><div>=A0 = =A0 Foo foo =3D new Foo();</div><div>=A0 =A0 write(foo.value);</div><div>= =A0 }</div><div>}</div> </div><div><br></div> --000325559162a095f404a681440b--
Jun 24 2011
On Sat, 25 Jun 2011 09:23:19 +0530, d coder wrote:Hello People I was just trying out custom memory allocation/deallocation that can be found on the link http://www.d-programming-language.org/memory.html#newdelete The problem is that the delete function is never getting called. I have put an example test case at the end of the email. Any ideas? Regards - Puneet
There is no guarantee that if and when the destructor or the custom delete will be called on garbage collected objects. If they do get called, the call order is not deterministic. You can define the objects as 'scope' to force their destructors to be called when exiting the scope:void main() { for (size_t i = 0; i < 32; ++i) { Foo foo = new Foo();
scope Foo foo = new Foo();write(foo.value); } }
Ali
Jun 24 2011
On 2011-06-24 23:01, Ali =C7ehreli wrote:On Sat, 25 Jun 2011 09:23:19 +0530, d coder wrote:Hello People =20 I was just trying out custom memory allocation/deallocation that can be found on the link http://www.d-programming-language.org/memory.html#newdelete =20 The problem is that the delete function is never getting called. I have put an example test case at the end of the email. =20 Any ideas? =20 Regards - Puneet
There is no guarantee that if and when the destructor or the custom delete will be called on garbage collected objects. If they do get called, the call order is not deterministic. =20 You can define the objects as 'scope' to force their destructors to be =20 called when exiting the scope:void main() { =20 for (size_t i =3D 0; i < 32; ++i) { =20 Foo foo =3D new Foo();
scope Foo foo =3D new Foo(); =20write(foo.value); =20 } =20 }
That version of scope is going away. Use std.typecons.scoped instead. =2D Jonathan M Davis
Jun 25 2011









Ali =?iso-8859-1?q?=C7ehreli?= <acehreli yahoo.com> 