It significantly predates the C++11 standard. Most of the smartpointers in the modern C++ standard weren't official until TR1 in 2003; even then, a lot of compilers took a long time to catch up. Prior to 2003, the only…
If that's straight-up bog-standard ANSI C++, then yes, there's a memory leak. But, to put my Devil's Advocate hat on a moment: the environment could be GCed and new could be overridden to return a GCed pointer, as…
As an observation, that's trivial: as an apologia, it's inadequate. I'm judging the author on what he said, not what other people think he really meant to say. If you change what the author said to be "C, C++ and Java…
Anybody who calls C, C++, and Java three of the most different programming languages out there is someone who has never tried LISP, Prolog, or SQL. He also flat says "C++ OOP has nothing to do with Java-like OOP", which…
It significantly predates the C++11 standard. Most of the smartpointers in the modern C++ standard weren't official until TR1 in 2003; even then, a lot of compilers took a long time to catch up. Prior to 2003, the only…
If that's straight-up bog-standard ANSI C++, then yes, there's a memory leak. But, to put my Devil's Advocate hat on a moment: the environment could be GCed and new could be overridden to return a GCed pointer, as…
As an observation, that's trivial: as an apologia, it's inadequate. I'm judging the author on what he said, not what other people think he really meant to say. If you change what the author said to be "C, C++ and Java…
Anybody who calls C, C++, and Java three of the most different programming languages out there is someone who has never tried LISP, Prolog, or SQL. He also flat says "C++ OOP has nothing to do with Java-like OOP", which…