[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: memory management

Keith Lucas wrote:

> It's all quite long and involved (about 1/3 of the book is about not leaking
> memory in one way or another), and does some FASCINATING stuff. {One idiom I
> loved so much I just rushed out and used it is a way of changing the type of
> an object at run-time... I used it to make arrays of things that actually
> aren't all the same object, which is handy at times.}

Changing the type of objects at runtime, as in dynamic_cast<> or
something else? Arrays of different objects is basic OOP, isn't it?

> Basically, it's all about using counting references, and making "new"
> innaccessible.

Does he talk about soft vs hard references and circular references? Does
the book talk about creation patterns, like pluggable factories and
metaclasses objects?

When I say C++ is crap, I know what I'm talking about. It can be made to
work, but it is creepy at best. Compared with the streamlined elegance
of Smalltalk or Objective-C, C++ looks like a clunky elephant.

Pierre Phaneuf
Ludus Design, http://ludusdesign.com/
"First they ignore you. Then they laugh at you.
Then they fight you. Then you win." -- Gandhi