Javac uses a "default" class path to its own classes (rt.jar or
classes.zip) and others it "knows" about. Jikes does not know about where
the classes are must be told explicitly in the classpath.
I am, very sincerely and truly,
your Friend and Well-Wisher,
Matt Smith
Sr. Software Engineer - Bui
At 08:48 AM 2/20/2001 +0100, Alain Muls wrote:
>Hello,
>
>I read about the jikes compiler and tried it out on a simple non
>graphical java application. It was fast and delivered the
>compiled code.
>I then tried it on a swing application with the same classpath
>settings as for javac (-classpath /
To: [EMAIL PROTECTED]
Subject: javac vs jikes
Hello,
I read about the jikes compiler and tried it out on a simple non
graphical java application. It was fast and delivered the
compiled code.
I then tried it on a swing application with the same classpath
settings as for javac (-classpath /my/path
Hello,
I read about the jikes compiler and tried it out on a simple non
graphical java application. It was fast and delivered the
compiled code.
I then tried it on a swing application with the same classpath
settings as for javac (-classpath /my/path/to/classes.zip) and
was amazed that jikes told
