There is some ambiguity in the docs regarding the mechanism for bypassing the GC. The section on memory management mentions that the new operator can
be overloaded. However, the sections on operator overloading, classes, as well as the entire D book does not mention this topic. Why is this?

-Debdatta Basu

On 26/11/2011 17:01, Debdatta wrote:
> There is some ambiguity in the docs regarding the mechanism for
> bypassing the GC. The section on memory management mentions that the
> new operator can be overloaded. However, the sections on operator
> overloading, classes, as well as the entire D book does not mention
> this topic. Why is this?
>
> -Debdatta Basu

I believe the plan is to remove the ability to overload new and delete, I forget the reasoning. You should post on the main newsgroup, digitalmars.D (or perhaps digitalmars.D.learn) if you want a real answer.

The best way (in general) to bypass the GC is to not use any features that depend on it - you're pretty limited as to what you can do then though.

-- 
Robert
http://octarineparrot.com/

Awesome :D

It would be interesting to know the reasoning behind this decision. It would be more interesting to know the reasoning behind including the feature in the first place. :D

And Robert, I have been developing a soft spot for D myself. It's got so many things right. And I am new to this forum, so I  would like to get a feel for the ecosystem.

Debdatta

Awesome! :D

It will be interesting to know the reasons behind this decision. More interesting would be the reasons behind including it in the first place. :D

And Robert, I have a huge soft spot for D too. It has got so many things right. So just wanted to hang out, watch the language evolve. Get a feel for
where it is headed.

Debdatta Basu.