devxlogo

Checking for Null After New (2)

Why Trust Us

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" : "notnull"));	}}

Then, try again with the commented body of the constructor.

Charlie has over a decade of experience in website administration and technology management. As the site admin, he oversees all technical aspects of running a high-traffic online platform, ensuring optimal performance, security, and user experience.

See also  How Engineering Leaders Spot Weak Proposals
Disclosure

About Our Editorial Process

At DevX, we’re dedicated to tech entrepreneurship. Our team closely follows industry shifts, new products, AI breakthroughs, technology trends, and funding announcements. Articles undergo thorough editing to ensure accuracy and clarity, reflecting DevX’s style and supporting entrepreneurs in the tech sphere.

See our full editorial policy.

Show More