malloc and new

[Mohsen]

Dear All,
Do you know if there is any difference between 'new' and
'malloc' in terms of handling memory?
If someone has insufficient memory to run a big problem, do you think
it makes any difference to use 'new' or 'malloc'?
Thanks,
Mohsen

 

[Ivan Vecerina]

: Dear All,
: Do you know if there is any difference between 'new' and
: 'malloc' in terms of handling memory?
It depends on the platform. But many implementations of
'new' just use malloc internally.

: If someone has insufficient memory to run a big problem, do you think
: it makes any difference to use 'new' or 'malloc'?
No (except for rare cases where you may benefit from 'realloc',
which is only available with the latter).


Can you tell more about the problem you are trying to solve?

 

[missdeer]

Some library will overload operator new, then the great differences exist.

 

[Jim Langston]

Dear All,
Do you know if there is any difference between 'new' and
'malloc' in terms of handling memory?
If someone has insufficient memory to run a big problem, do you think
it makes any difference to use 'new' or 'malloc'?
Thanks,
Mohsen

Typically, it wouldn't matter, as most default implementations of new use
malloc under the seams. However, you are free to create your own
implementation of new, in which case it could make a diffeence depending on
what you did (I could forsee someone using memory sticks).

 

[Ron Natalie]

Dear All,
Do you know if there is any difference between 'new' and
'malloc' in terms of handling memory?
If someone has insufficient memory to run a big problem, do you think
it makes any difference to use 'new' or 'malloc'?
Thanks,
Mohsen

new crates objects.
malloc allocates bytes of memory.

New has a return type of something other than void*.
New can have the memory allocator swapped out (operator new overloaded)
New performs initialization of most types.
New performs "behind-the-scenes" types of initialization like
setting up run-time typing.