News for hackers. Stuff that matters.
Re:Three bad things: threads, garbage collection, and nondet... by acqq on Tuesday August 17, 2010 @03:11AM (#1610478)
It's still bad, since it will lead to the effect "just write every class with auto."

C++ combined memory allocation and the object destruction in one thing and now we have too many people that think those should be one primitive. They shouldn't. Once you recognize that you have to care about both separately, you start to recognize that even GC is an answer to the wrong question.

For really "cool" programs (using the most of the resources etc) you simply have to manage memory yourself. Object should not manage their allocation, they should just "know" who's in charge for their allocation.

Some Bloomberg guys recognized that and made some libraries for C++, ans some work was done to get something like that in C++ standard, but I don't know if the result is useful.

I also don't know if such ideas would look nicer in D.

There are no comments on this comment yet.