From: Tom Tromey <tromey@redhat.com>
To: Christophe Roux <ch_roux@club-internet.fr>
Cc: rhug-rhats@sources.redhat.com
Subject: Re: gcj minor bug
Date: Fri, 13 Dec 2002 13:48:00 -0000 [thread overview]
Message-ID: <87pts57fqt.fsf@fleche.redhat.com> (raw)
In-Reply-To: <E18MxJl-0005Kt-00@smarthost2.mail.easynet.fr>
>>>>> "Christophe" == Christophe Roux <ch_roux@club-internet.fr> writes:
Christophe> In fact, I discovered a bug in gcj by the way : The class
Christophe> StringTokenizer, when returning all tokens ( also
Christophe> separators ), gives empty tokens for separators;
This is a well known gcj bug. The code in StringTokenizer is actually
fine, it is the compiler that has the problem. I believe this bug is
fixed in cvs.
Christophe> But I read the steps needed to contribute to gcj, and my
Christophe> reaction is : It is very complicated to contribute.
We try to make it easy. For simple patches, just send the patch, a
ChangeLog entry, and an explanation to <java-patches@gcc.gnu.org>.
If you submit several small patches, or one large one, you'll have to
go through the whole paperwork thing.
Tom
prev parent reply other threads:[~2002-12-13 21:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-13 13:26 Christophe Roux
2002-12-13 13:48 ` Tom Tromey [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pts57fqt.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=ch_roux@club-internet.fr \
--cc=rhug-rhats@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).