Defining a custom *constructor* (not initializer!)

Mehrdad wfunction at
Mon May 7 12:09:34 PDT 2012

Oh, and ditto with the destructor: I need to be able to call the 
destructor manually, because the C does that inside a callback on 
my behalf.

On Monday, 7 May 2012 at 19:08:18 UTC, Mehrdad wrote:
> No, I *am* placing it on the heap.
> I'm just asking if I can call the constructor manually, because
> (like I wrote in my first post...) sometimes the C code you're
> interoperating with takes control away from you, and just calls 
> a
> callback on your behalf when constructing the object.
> (Yes, I realize there are different solutions to this problem.
> They're just not as elegant.)

More information about the Digitalmars-d mailing list