> From: Brian Jones
> Subject: japhar bug
>
>
> Japhar cannot compile GNU Classpath. To be specific, it can currently
> compile simple Hello type programs and some parts of GNU Classpath,
> but bombs during the current compile with this error. I believe this
> happens when Japhar has to compile many classes on the same command
> line due to multiple dependencies between the classes. Given that
> Japhar uses Sun's javac then there is something weird going on in the
> VM.
>
> ../java/lang/Throwable.java:124: Class
> java.io.ObjectOutputStream. PPPPPPPP not found in type declaration.
> ObjectOutputStream.PutField oFields;
> ^
> ../java/lang/Throwable.java:136: Class
> java.io.ObjectInputStream. GGGGGGGG not found in type declaration.
> ObjectInputStream.GetField oFields;
> ^
> ../java/util/AbstractCollection.java:63: Class
> java.lln.lln.lln.lln.lln.lln.lln.lln.ll not found in type declaration.
> throw new java.lang.UnsupportedOperationException();
> ^
> 3 errors
>
A little additional note about this bug: this appears to be a bug in
some sort of a classname string copy operation. Note that the "PPPPPPPP" is
the same size as "PutField" and "GGGGGGGG" is the same size as "GetField."
This may be a red herring, however, since
"lln.lln.lln.lln.lln.lln.lln.lln.ll" is not the same size as
"UnsupportedOperationException". The first two cases deal with inner
classes, though, and the last one deals with a top-level class, so perhaps
they're different problems after all.
--John Keiser