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: Java
Expertise: Intermediate
Sep 13, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Checking for Null After New

In lot of places, I have seen developers doing a 'new' to instantiate a user-defined data type (Objects) and then later in the source code checking whether this new Object is referring to null or not by doing a (Object == null).

This check is not required in Java because 'new' is not allowed to return null.

A new operator will raise an OutOfMerroryException if there is insufficient memory available.

Mahesh Chulet
 
Comment and Contribute

 

 

 

 

 


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

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date