• anonymous
In Java, when to use import java.util.*; versus import java.Scanner;
Computer Science
  • Stacey Warren - Expert
Hey! We 've verified this expert answer for you, click below to unlock the details :)
At vero eos et accusamus et iusto odio dignissimos ducimus qui blanditiis praesentium voluptatum deleniti atque corrupti quos dolores et quas molestias excepturi sint occaecati cupiditate non provident, similique sunt in culpa qui officia deserunt mollitia animi, id est laborum et dolorum fuga. Et harum quidem rerum facilis est et expedita distinctio. Nam libero tempore, cum soluta nobis est eligendi optio cumque nihil impedit quo minus id quod maxime placeat facere possimus, omnis voluptas assumenda est, omnis dolor repellendus. Itaque earum rerum hic tenetur a sapiente delectus, ut aut reiciendis voluptatibus maiores alias consequatur aut perferendis doloribus asperiores repellat.
  • schrodinger
I got my questions answered at in under 10 minutes. Go to now for free help!
  • e.mccormick
When you finish a java project it should onlu include what is needed if you do the .*, however, you won't know what is actually used and included. By doing spesific includes you have a better idea of what is going into a pogram wheich can result in knowing what can be done to improve it. Also, if you add something later you will have an idea of what is already inclided so ready to use, thus preventing the addition of similar libraries that would increase size for little or no feature. With that in mind, when do you think it would be better to use the generic * rather than specific things?

Looking for something else?

Not the answer you are looking for? Search for more explanations.