How can you tell when a Java import statement uses wildcard matching?

Question

I asked a previous question which is apparently a duplicate of this question. I always thought that asterisks were the only way to denote wildcard matching in import statements.

What causes either of the import statements

import android.util.Log;

or

import android.os.Environment;

to be interpreted as patterns that could match multiple packages? Or is there some other definition of wildcard matching that I don't understand?

Please help!

The same way it would take google to auto fill your search when you type something in the search bar...An algorithm!!! :) — ryekayo, Mar 21 '15 at 00:24
Sometime questions are closed for dumb reasons... SO users are humans. — user253751, Mar 21 '15 at 00:26
For what it's worth your question has 2 votes to reopen it (I think 4 or 5 are required) — user253751, Mar 21 '15 at 00:27

score 1 · Accepted Answer · answered Mar 21 '15 at 00:29

I always thought that asterisks were the only way to denote wildcard matching in import statements.

They are.

What causes either of the import statements import android.util.Log; or import android.os.Environment; to be interpreted as patterns that could match multiple packages?

Nothing. They are not.

Or is there some other definition of wildcard matching that I don't understand?

Not per se.

But looking at your other question, it seems like the real problem is with the classpath that is being used when InetAddress.java is being compiled.

How can you tell when a Java import statement uses wildcard matching?

1 Answers1