From: "Tony Ingenoso" 

Objectified C++ still has some significant bloat/performance issues IMO, in
some cases the penalty over a standard C equivalent can be dramatic. 
There's places where I'd not chose it, others where I would, and others
where I'd use neither C++ or C.

I blame C/C++ for a lot of the flakiness in modern code.  For most people
writing in them it like handing a scalpel to a 3 year old to play
with...the results can be messy ;->

"Paul Ranson"  wrote in message
news:3ee08f6b$1{at}w3.nls.net...
> 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

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