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: All
Jul 14, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Don't Import All Items

The import directive in Java can sometimes be confusing. For example, if you put this line at the top of your source file:

 
import java.util.*;

Do all the classes in the java.util package get loaded into your program? The answer is no; all the import statement does is let your program find the classes in the package. The classes are only loaded when they are used in the code. So, if you have these statements in your code, the classes Vector and Hashtable will be loaded by the VM when it reaches this point in the code. The other classes under java.util are not loaded.

 
Vector v = new Vector;
Hashtable h = new Hashtable();

However, using the "*" to declare the imports reduces the clarity of your code. For example, just by looking at the statement "import java.util.*," you really don't get any idea of the classes actually used in the program. A better way to declare imports is to declare the fully qualified class. For the example given here, your imports should look like:

 
import java.util.Vector;
import java.util.Hashtable;
Ajit Sagar
 
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