How the GC distinguishes code from data

%u wfunction at
Fri Jan 7 09:47:33 PST 2011

> It assumes everything on the stack is pointers, at the moment, I believe

Uh-oh... not the answer I wanted to hear, but I was half-expecting this.
So doesn't that mean that, at the moment, D will leak memory?

> If it's not on the garbage collected heap, it won't scan it unless you
tell it to.

But what if it's a void[] on a non-GC heap? Doesn't the language say that needs to
be scanned too?

More information about the Digitalmars-d-learn mailing list