Shortcut notation

[Charles Angemeyer]

Recently I was experimenting with Bufferedreader and came across a web example that you see below.
(I only included the top part of the code).
My question is this: Wouldn't I want to use some abreviation notation for the import statements?
Wouldn't import.java.io.* be better than listing each out individually? Many thanks.

package readingafile;

import java.io.BufferedReader;
import java.io.FileReader;
import java.io.IOException;
 
public class ReadingAFile {
 
	public static void main(String[] args) {
 
...

[Winston Gutkowski]

Charles Angemeyer wrote:My question is this: Wouldn't I want to use some abreviation notation for the import statements?
Wouldn't import.java.io.* be better than listing each out individually?

You certainly can, but I tend not to; and it sounds like you're probably using an IDE, most of which create them as you've shown.

I guess my question to you is: why would you bother? The savings are ONLY at compile time (and even then we're talking milliseconds); it makes absolutely no difference whatsoever to your runtime class.

Winston

[Campbell Ritchie]

Using individual imports has two advantages.

1: You have a list of classes (etc) used in your application (or at least in the current class).

2: There is less risk of collisions, eg between Timers.

[Bear Bibeault]

Campbell Ritchie wrote:Using individual imports has two advantages.

1: You have a list of classes (etc) used in your application (or at least in the current class).

2: There is less risk of collisions, eg between Timers.

This. I always list them out individually. My IDE can hide them during editing if they seem to be in the way, but that is rare.