Re: Slightly OT: Compilation question
Paul Hsieh wrote:
On Jun 13, 8:15 pm, Keith Thompson <ks...@mib.org> wrote:
Paul Hsieh <websn...@gmail.com> writes:
It also
forces you to be more exact in function declarations. This I
found to be the biggest actual source code impact, as it
basically forces you to cast all mallocs.
Right (but it's usually better practice to use new and delete in
C++ anyway, or some STL type that manages memory for you).
C++ is built on the RAII principle. Using new and delete invoke
constructors which you might not want to happen. Furthermore, its
easy to show that STL's vector templates have either ridiculously
bad performance in comparison to hand managed realloc()'s precisely
because of the RAII overhead or else compromise your design to the
point that you might as well use realloc().
Constructors are invoked for types that have constructors. How do you
do that with realloc?
I.e., its not surprising that malloc/free has not been and will not
be deprecated in the C++.
Is it?
Bo Persson