🚀 go-pugleaf

grantp@usa.pipeline.com(Pete) wrote:

[ I've trimmed the newsgroups since this seems to have little to do with
compatibility of applications... ] 

>On Jan 28, 1996 01:54:41 in article <Re: HELP !!! Memory - Allocation>,
>'urcrawfo@mcs.drexel.edu (Programmer)' wrote: 
> 
>>It is highly recommended using the "new" operator when using C++. 
>>It is both practical and effifienct. 
>> 
>I agree with the recommendation; however, just to set the 
>record straight :-) 
> 
>On some systems, notably g++ 2.6.3, new performs a few  
>instructions of its own, then calls malloc.  This leads me to 
>conclude that new is less efficient than a direct call to  
>malloc -- although the margin is probably very narrow. 

This depends heavily (perhaps completely) on the situation.  This may be
how g++ 2.6.3 implements global operator new, but the program can
redefine this as needed on either a global basis (rarely reccomended) or
for particular classes.  In the latter case new may be, and often is,
considerably more efficient than malloc.