From: "Robert Comer" 

> You can leak memory and resources in a garbage collected environment. And
> these leaks will be more insidious than a straightforward C++ memory leak.

They can be but I don't think I'd say they would be, especially when C++
can have the same type too.

> Without the risks you don't get the rewards.

Just what rewards can I get here that I can't get from a better designed
language, size of executables don't matter anymore, I/O is still the drag
on everything so raw execution speed doesn't interest me, object oriented
can be done in a LOT of other languages, code reuse can be done better in
other languages.  For OS stuff, there sure have been a lot of exploits to
think that C++ is really where we want to go for secure computing...

- Bob Comer


"Paul Ranson"  wrote in message
news:40222dc7$1{at}w3.nls.net...
> You can leak memory and resources in a garbage collected environment. And
> these leaks will be more insidious than a straightforward C++ memory leak.
> With the latter any modern development environment will just tell you what
> you leaked and where it was allocated.
>
> Without the risks you don't get the rewards.
>
> Paul
>
> "Robert Comer"  wrote in message
> news:4021bccf$1{at}w3.nls.net...
> > > I think what he's saying is you are attributing it to the language
> instead
> > > of the programmer. I can write bad code in a dozen different
languages..
> >
> > I know what he's saying, I just don't agree. (C++ increases risk that
> > doesn't need to be there.)
> >
> > - Bob Comer
> >
>
>

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