dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: C++
Expertise: Beginner
Feb 14, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


New Versus Malloc()

Question:
Why is it necessary to typecast the return value of malloc() but not for the new operator?

This question has been asked of many C++ experts but no one has given me a convincing answer.

Answer:
Unlike malloc(), operator new is aware of the type of the object it allocates because it needs to invoke the class' constructor before returning the allocated object's address. Since new is aware of the actual type of object being allocated, it automatically casts the returned pointer to the desired type for you.

By contrast, malloc() doesn't know which type of object it allocates. Therefore, when using malloc(), you need to specify the size of the object explicitly, as well as cast the returned pointer to the desired type.

This is a fertile source of errors; therefore, it's best to avoid using malloc() in C++ altogether.

DevX Pro
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
×
We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date