Date ambiguity at go4java

[Bill Tripper]

From http://www.go4java.20m.com/index.htm I encountered the following question:
Q27.What will be the result of compiling and running the given program?
Select any two.

  import java.util.*;
  import java.sql.*;
  class Q27
  {
     Date d=new Date();
     public static void main(String arg[])
     {
     }
  }

1. Compile time error as Date class is defined in both of the above packages.
2. Run time error as Date class is defined in both of the above packages.
3. It will compile and run without any error.
4. It will compile and run if we use .Date instead of .* in any one of the two import statements
The answers given are 1 and 4. I believe that answer 4 is incorrect. If you change the import statement to "import java.sql.Date", then you get a compile error as the java.sql.Date class specifies no constructor without an argument. That is, you can't have "java.sql.Date d = new java.sql.Date()". Of course, if you specify "import java.util.Date", then the program will compile.
Bill

[Asma Zafar]

you're absoulutely right Bill. Choice 4 is incorrect unless it explicitly mentions importing java.util.Date.

Asma Zafar,
Sun Certified Programmer for Java2 platform.
[This message has been edited by Asma Zafar (edited August 25, 2001).]