<<0>>-<>-<>-<>-<<0>>
XML developer resources written in Japanese
Go to the developerWorks XML Zone to find XML development articles,
white-papers, and tutorials written in Japanese. At the dW XML Zone
You can get over 40 pieces of XML content that is Written in Japanese.
dW Japan XML Zone - de
I've seen this before on redhat 7.0 and it is logged on the redhat
bug page as a known bug, currently they had fixed it in 7.1 but have
not issued a patch to 7.0
RedHat bug Id: 23758
location: http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=23758
The classic VM in 1.3 does return the expect
> "Joseph" == Joseph Shraibman <[EMAIL PROTECTED]> writes:
Joseph> Juergen Kreileder wrote:
>> Please note that it is perfectly legal with respect to the JLS
>> to implement Thread.yield() as nop in JVMs based LinuxThreads.
>> Actually it is not only legal, it's desirable to i
On Mon, 12 Feb 2001, Dan Kegel wrote:
> Hi,
> looks like System.exit(1) doesn't cause the java executable to
> terminate with an exit status of 1 with the Blackdown 1.3.0.
There is a bug open on this on Sun's BugParade. Some versions of the
Linux pthreads library trigger issues when the thread
On Mon, 12 Feb 2001, Calvin Austin wrote:
> There are some 1.3 hotspot related jdb bugs for example the one listed
> below. If you happen to come across one I would recommend using the classic
> VM (jdb -classic) until those bugs are fixed
Yes, I've seen those. However, I've tested Sun 1.2.2 fo
Hi,
looks like System.exit(1) doesn't cause the java executable to
terminate with an exit status of 1 with the Blackdown 1.3.0.
It works fine with the IBM 1.3.0, though. Here's my test program:
import java.io.*;
public class foo {
public static void main(String args[]) {
Joseph Shraibman wrote:
> > Please note that it is perfectly legal with respect to the JLS to
> > implement Thread.yield() as nop in JVMs based LinuxThreads. Actually
> > it is not only legal, it's desirable to implement it as nop on JVMs
> > that employ preemptive scheduling policies (especiall
There are some 1.3 hotspot related jdb bugs for example the one listed
below. If you happen to come across one I would recommend using the classic
VM (jdb -classic) until those bugs are fixed
regards
calvin
Joi Ellis wrote:
>
> On Sat, 10 Feb 2001, Jesus M. Salvo Jr. wrote:
>
> > I had more su
Juergen Kreileder wrote:
>
>
> Please note that it is perfectly legal with respect to the JLS to
> implement Thread.yield() as nop in JVMs based LinuxThreads. Actually
> it is not only legal, it's desirable to implement it as nop on JVMs
> that employ preemptive scheduling policies (especially
It's not JDK ... but I think I remember seeing reports
that GCJ may be working on ARM. Unless you
need Swing, check it out at http://gcc.gnu.org/java/ ...
if it's not running on ARM, a couple good engineers
should be able to make a solid dent in that problem!
Evidently the "libffi" support (in by
On Sun, 11 Feb 2001, Dimitris Vyzovitis wrote:
> > I'm not sure what you want to show with test_fairness. You have three
> > threads which all count up to the same number. Then finally you print
> > out the three counters which always will be the same. There's nothing
> > in this code testin
Subject says it all - what is the status of the port?
If no one is doing it, can anyone comment on the size of
the task: what has to be done, if it is feasible for a couple
of good SW engineers to knock over quickly?
--
To UNSU
begin:vcard
n:Juarez Martinez;Fco. Javier
x-mozilla-html:TRUE
fn;quoted-printable:Fco. Javier Juá=3BrezeresMas Dpto Ingenieria y Desarrollo
org:http://www.eresmas.com">http://eventos.eresmas.com/evento145/img/banner_eresmas.gif" border="0" alt="[eresMas]">
adr:;;
version:2.1
email;internet
13 matches
Mail list logo
