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
Dec 14, 2001

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Checking for Null After New (2)


Normally, you should not check for null after creating an object.
 
MyObject o = new MyObject();

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. But if an object constructor has generated an Exception, the object hasn't been created. Try this simple code:
 
public class test {
	public test() throws Exception {
		throw new Exception("Exception in _
constructor");
	}

	public static void main(String s[]) {
		test t = null;
		try {
			t = new test();
		} catch (Exception e) {
			System.out.println(e.toString());
		}
		System.out.println("The instance is " + _
((t == null)? "null" : "not
null"));
	}
}

Then, try again with the commented body of the constructor.
Mike Dudenko
 
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