I’m not trained in Java, but do write experimental programs with it. Here are some ideas about the import statement, as I understand it:<\/p>\n
Herein, it might be helpful to think of a package<\/em> as a directory<\/em>.<\/p>\n The Java statement<\/p>\n import pckg0.member0;<\/span><\/p>\n gives access to the definition of member0<\/span>, as needed for the program. In this context, member0<\/span> is a single, specific class<\/em> found in the package<\/em> pckg0.<\/span><\/p>\n The statement<\/p>\n import pckg0.*;<\/span><\/p>\n gives access to all “single” classes contained in pckg0<\/span>, but not to those of its subdirectories. If pckg0<\/span> contains the package pckg00<\/span>, which contains the class mem01<\/span>, then the statement<\/p>\n import pckg0.pckg00.mem01;<\/span><\/p>\n provides access to it.<\/p>\n The statement<\/p>\n import pckg0.pckg00.*;<\/span><\/p>\n provides access to all single classes in pckg00<\/span>.<\/p>\n Therefore, the two import statements, one atop the other,<\/p>\n import pckg0.*;<\/span> can sensibly occur together at the top of a Java program.<\/p>\n HTH:)<\/p>\n Source:<\/p>\n McGrath, Mike. Java in Easy Steps<\/u>, 5th ed. Warwickshire: Easy Steps Limited, 2014.<\/p>\n docs.oracle.com<\/a><\/p>\n
\nimport pckg0.pck00.*;<\/span><\/p>\n