From: "Paul Ranson" 

I've no problem with old code, but I see no point in writing new code in an
old style.

Obviously malloc() is available and usually where 'new' ends up, but it's
not a requirement. There are many interesting optimisation strategies
available with different allocation strategies.

Paul

"Tony Ingenoso"  wrote in
message news:3edffa9e{at}w3.nls.net...
> Good old code won't have those problems, bad old code will.  C++ has
plenty of opportunity for memory leaks BTW - what do you
> suppose the 'new' RTL workers are calling under the covers?  stodgy old
malloc()
>
> "Paul Ranson"  wrote in message
news:3ede2aec{at}w3.nls.net...
> > ...20 year old styles? There's nothing cool about leaving oneself open
to
> > memory leaks and buffer overruns.
>
>

--- BBBS/NT v4.01 Flag-4