public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/16281] New: JNI accepts illegal Class Descriptors
Date: Tue, 29 Jun 2004 22:14:00 -0000	[thread overview]
Message-ID: <20040629203308.16281.mark@gcc.gnu.org> (raw)

JNI Class Descriptors look like Lclass/name/with/dot/replaced/by/slash;
Ljava/lang/String; is a legal JNI Class Descriptor, but Ljava.lang.String; is
not. The second form is accepted in for example Method Descriptors given to
GetMethodID as shown in this email:
http://gcc.gnu.org/ml/java-patches/2004-q2/msg00831.html

It would be nice if there was at least a warning that non-standard Class
Descriptors are accepted since this will likely fail on other JNI
implementations (like the jamvm one).

-- 
           Summary: JNI accepts illegal Class Descriptors
           Product: gcc
           Version: 3.5.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P2
         Component: libgcj
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: mark at gcc dot gnu dot org
                CC: gcc-bugs at gcc dot gnu dot org,java-prs at gcc dot gnu
                    dot org


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16281


             reply	other threads:[~2004-06-29 20:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-29 22:14 mark at gcc dot gnu dot org [this message]
2004-06-30  3:30 ` [Bug libgcj/16281] " mckinlay at redhat dot com
2004-06-30  8:50 ` mckinlay at redhat dot com
2005-09-04 12:20 ` mark at gcc dot gnu dot org

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=20040629203308.16281.mark@gcc.gnu.org \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@gcc.gnu.org \
    /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).