On Wed, 6 Sep 2000, Jon Stevens wrote:
> I'm sorry that is has been frustrating, but for a number of weeks now I have
> been posting about how things are in a state of flux. You should realize
> that you are working on bleeding edge technology and should expect things to
> be broken once and a while. Of course, we are doing our best to work our
> asses off to make things better for you. In case you missed it, this is a
> volunteer project and we depend on those volunteers to make this thing work.
> If it isn't working, then become a volunteer and help out.
alternatively I posted a build file and some simple changes
a couple of days ago that makes things *much* easier IMHO -
look it up via archives.
> In Java, dependencies are resolved by the compiler. If you are using Jikes,
> it blows when it comes to dependencies for the first compile. If you are
> using javacc, it actually does things correctly.
What exactly is jikes doing wrong ? The only errors I know
of for jikes has to do with either bad debugging info in
.class files or bad usage. Every other case it has been
javac at fault - so what problems does it cause ? And are
you using latest jikes ??
Cheers,
Pete
*--------------------------------------------------*
| Latrobe University, | Does the name 'Pavlov' |
| Bundoora, Australia | ring a bell ? |
*--------------------------------------------------*
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
