Name: mc57594 Date: 03/07/97


Bug 1:

Create a .java file with two class definitions whose names differ
only in case. Compile it. Only one .class file is generated. The
compiler should generate a warning in this case. (It can,
after all, examine the directory to find the case-sensitive file
name even if the OS ignores case when opening the file.)

Bug 2:

Create a foo.java file with a foo class defined in it.
Compile it. Rename the class file too bogus.class. The VM
happily lets me instantiate an instance of class bogus and
send it messages. The VM should at minimum check that the
class name it thinks it loaded is the one defined in the
.class file. This would solve the eariler problem as well
(or at least give me a reasonable error message).


company - Holub Associates , email - ###@###.###
======================================================================