public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: gbenson@redhat.com
To: gcc-gnats@gcc.gnu.org
Subject: java/8893: Local classes are named incorrectly
Date: Tue, 10 Dec 2002 10:26:00 -0000	[thread overview]
Message-ID: <20021210181842.5381.qmail@sources.redhat.com> (raw)


>Number:         8893
>Category:       java
>Synopsis:       Local classes are named incorrectly
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Tue Dec 10 10:26:08 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     gbenson@redhat.com
>Release:        gcc-3.2 patched for PR 1343
>Organization:
>Environment:
Red Hat Linux 8.0
>Description:
The fix for PR 1343 is broken: although the names of local classes are prepended by a number, only one counter is used per source file.  For example, the following code:

| public class Test {
|     public void func1() {
|         class Foo {
|         }
|         class Bar {
|         }
|     }
|     public void func2() {
|         class Foo {
|         }
|     }
| }

compiles to Test.class, Test$1$Foo.class, Test$2$Bar.class and Test$3$Foo.class instead of Test.class, Test$1$Foo.class, Test$1$Bar.class and Test$2$Foo.class.

>How-To-Repeat:
gcj Test.java # attached
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:
----gnatsweb-attachment----
Content-Type: application/octet-stream; name="Test.java"
Content-Transfer-Encoding: base64
Content-Disposition: attachment; filename="Test.java"

cHVibGljIGNsYXNzIFRlc3QgewogICAgcHVibGljIHZvaWQgZnVuYzEoKSB7CgljbGFzcyBGb28g
ewoJfQoJY2xhc3MgQmFyIHsKCX0KICAgIH0KICAgIHB1YmxpYyB2b2lkIGZ1bmMyKCkgewoJY2xh
c3MgRm9vIHsKCX0KICAgIH0KfQo=


             reply	other threads:[~2002-12-10 18:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 10:26 gbenson [this message]
2002-12-10 11:36 Eric Blake
2002-12-10 18:46 Tom Tromey
2002-12-11  3:06 Gary Benson
2002-12-11  9:43 tromey

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=20021210181842.5381.qmail@sources.redhat.com \
    --to=gbenson@redhat.com \
    --cc=gcc-gnats@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).