🚀 go-pugleaf

In article <425akd$4r7@status.gen.nz>, sarge@iconz.co.nz says...
>
>In article <809779542snz@onex.demon.co.uk>, Martin@onex.demon.co.uk says...
>>
>>OK, here's a new one to throw into this thread - but not totally un-related.
>>Which is faster new or malloc ? My C++ book says that new should be faster.
>
>More to the point is the fact that you shouldn't ever use malloc for 
>user-defined types.  The reason is that new will call constructors (and 
>delete will call destructors).  malloc() is okay for built-in types but don't 
>use it otherwise.  
>The second point is that new is type safe.  malloc() returns a void * which 
>you then have to cast (except you don't => big hole in typing system).
>
>In conclusion don't use malloc.
>
The third point is that with new, you can define your own allocators on a per-class basis, so 
that you can optimized your memory allocation scheme (can you say cache?) without modifying the 
code that uses a class. 





-- 
The opinions expressed in this message are my own personal views 
and do not reflect the official views of Microsoft Corporation.