[EMAIL PROTECTED] writes:
> That's too bad that importscrubber messed up the Scarab source code.
> Importscrubber is still definitely a work in progress, and there are some
> things that it is definitely going to miss. For example, since the
> compiler inlines references to static finals, and importscrubber looks in
> the class file for class references.... it's going to miss those
> references. Which is unfortunate. Also, if a string looks a lot like a
> class name, Importscrubber may think its a class name and try to turn it
> into an import statement.
When writing JNI code which references Java classes, one has to use
special markup on the fully qualified class names.
I.e. "Lorg/apache/turbine/Turbine;" would be the string literal
corresponding to the class org.apache.turbine.Turbine, and something
like "(Ljava/lang/String;Ljava/lang/String;)V" to denote a method
which takes two String parameters. Looking at some bytecode using
`strings`, I notice that this seems to apply to at least part of a
method signature. Not a lot of help here, but maybe something to
think about. <shrug/>
Dan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
