Mark Wielaard wrote:
Hi,
The HACKING file says:
- IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
I am using jikes Version 1.15 - 26 Sept 2001 and didn't notice any
errors. Does anybody remember why we don't recommend jikes 1.13?
With Wonka we've had problems with every
hi all,
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this subject.
bye
Jakob
___
Classpath mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/classpath
Jakob Praher [EMAIL PROTECTED] writes:
hi all,
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this subject.
I have done a little bit of work for GCJ with this.
Unfortunately I haven't had any time recently to
Am Mon, 2002-02-04 um 18.39 schrieb Nic Ferrier:
Jakob Praher [EMAIL PROTECTED] writes:
hi all,
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this subject.
I have done a little bit of work for GCJ
Jakob Praher [EMAIL PROTECTED] writes:
Am Mon, 2002-02-04 um 18.39 schrieb Nic Ferrier:
Jakob Praher [EMAIL PROTECTED] writes:
hi all,
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this
Hi,
The HACKING file says:
- IBM jikes 1.13 (newer versions up to 1.15 appear to be broken)
I am using jikes Version 1.15 - 26 Sept 2001 and didn't notice any
errors. Does anybody remember why we don't recommend jikes 1.13?
With Wonka we've had problems with every version
John Leuner wrote:
There were issues (don't remember exactly what), but I've been using
the jikes 1.15 in debian/unstable and it seems to work fine. (I have
compiled all of classpath with it)
FWIW, I had to put jikes in debian/unstable on hold at 1.14-0.4 because
it started doing nasty
Hi,
On Mon, 2002-02-04 at 18:27, Jakob Praher wrote:
Am Mon, 2002-02-04 um 18.39 schrieb Nic Ferrier:
Jakob Praher [EMAIL PROTECTED] writes:
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this subject.
Hi,
Chris Gray wrote:
With Wonka we've had problems with every version after 1.12.1 (!).
Problems includes: dumps core on valid input, outputs illegal
bytecode
Stuart Ballard wrote:
FWIW, I had to put jikes in debian/unstable on hold at 1.14-0.4 because
it started doing nasty things to my
Mark Wielaard wrote:
I have read the online 1.4 specs for java.nio and thought about how to
implement it but I have done no actual work. We will get it in time, but
nobody is actively working on it at the moment.
For me, most tricky parts of nio is Buffer. You have to extend JNI to
enable
I'm one of the jikes developers. I know that Jikes 1.15 has some
problems compiling inner classes with private constructors, (jikes
compiles with exit status 0, but execution of the resulting .class file
causes a VerifyError), and there are a few of those in Classpath. I'm
not sure if the
Hi,
On Mon, 2002-02-04 at 22:19, Artur Biesiadowski wrote:
Do you think that Buffers should be a part of classpath ? Or should they
be left for jvm implementors ? There is quite a lot of code there - all
kinds of wrapper classes, splitting, views etc. But on the other hand,
core get/set
Mark Wielaard wrote:
do you have any plan on adding nio support and asynchronous io to the
classpath project?
if yes what is your agenda on this subject.
I have done a little bit of work for GCJ with this.
I have read the online 1.4 specs for java.nio and thought about how to
implement it
Mark Wielaard wrote:
Have people with jikes problems actaully reported them to the jikes
developers? We can try to recompile Wonka with 1.15 to see what happens.
Stuart, what program were you using which forced you to downgrade to
1.14?
The problems I encountered were in a program written
Mark Wielaard [EMAIL PROTECTED] writes:
OK. So it seems that we can recommend jikes 1.15 for compiling Classpath
but it may have some problems for other applications. I will put that in
the HACKING and INSTALL notices.
There were also problems with compiled constants (final static) using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry for the X-post.
I just created a new mailing list:
[EMAIL PROTECTED]
You can sign up here:
http://entropy.yi.org/cgi-bin/mailman/listinfo/java-is-dead
...
Are you upset at the way Java is being handled by SUN?
Do you feel lied to
From: Artur Biesiadowski [EMAIL PROTECTED]
For me, most tricky parts of nio is Buffer. You have to extend JNI to
enable them, make some special tricks in jvm to allow them to work with
acceptable speed.
Do you think that Buffers should be a part of classpath ? Or should they
be left for
17 matches
Mail list logo
