[EMAIL PROTECTED] wrote:
> Sinz writes:
>
> CLASSPATH, as it is currently implemented by various JVMs, JDKs, and
> browsers is, IMHO, one of the most confusing, broken, and expensive
> problems in Java (expensive in the cost of support and the like)
>
> I couldn't agree more. It's the most frequent source of confusion to users
> of the Jikes compiler.
>
> dave
> [EMAIL PROTECTED] http://www.ibm.com/research/jikes
Thankfully, between the extensions mechansim, the "java -jar" option,
and the
ability for .jar's to specify their own *relative* classpaths, CLASSPATH
will
hopefully be more or less fixed in JDK 1.2 (at least at the deployment
end of
things).
Of course it also means problems for third party tools like jikes, who
will
have to find some other way of locating the jdk core classes and
extensions since
CLASSPATH shouldn't be used for this anymore.
regards
[ bryce ]
