large Class.forName() patch

[Mo DeJong]

Ok, if you have a class named "int" then the JVM should load
that when you call forName("int"). I am not sure what Kaffe
would do in this case because it already uses the name "int"
for the primitive class "I". I think the best way to make
the regression test check for this is to ensure that
a loaded class (like "int") is not a primitive type.

Mo Dejong
Red Hat Inc.

On Mon, 31 Jan 2000, Patrick Tullmann wrote:

> I ran ArrayForName on JDK 1.2.2 on Solaris.  Got this output:
> 
> for clsName "int" expected "Exception" but got "int"
> for clsName "[Lint;" expected "Exception" but got "int[]"
> 
> Note that I had a (legit) class called 'int.class' in my current
> directory when I ran the test.  Loading 'int' does *not* load the
> Integer class or the primitive 'int' class, but it *will* load some
> arbitrary class called 'int'.  So the explicit denial of 'int' classes
> is wrong.
> 
> -Pat