public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ashe@qms.com
To: java-gnats@sourceware.cygnus.com
Subject: java/1455: gcjh barfs on legal java name usage
Date: Wed, 20 Dec 2000 12:28:00 -0000	[thread overview]
Message-ID: <19991022233419.31153.qmail@sourceware.cygnus.com> (raw)

>Number:         1455
>Category:       java
>Synopsis:       gcjh barfs on legal java name usage
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    apbianco
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Dec 20 12:20:08 PST 2000
>Closed-Date:    
>Last-Modified:  Thu Nov  4 21:16:00 PST 1999
>Originator:     Steven Ashe
>Release:        2.95.1 and later
>Organization:
>Environment:
linux rh6.0
>Description:
run this legal Java through gcjh:

class Foo {
    public static int  F;

    public void  F() {
    }
}

result is:
static field has same name as method   
>How-To-Repeat:
see "Description"			
>Fix:

>Release-Note:
>Audit-Trail:

Formerly PR gcj/75


From: Tom Tromey <tromey@cygnus.com>
To: Java Gnats Server <java-gnats@sourceware.cygnus.com> 
Cc:  
Subject: gcj/75
Date: 04 Nov 1999 22:20:24 -0700

 Thanks for the report.  This is a known bug.  The problem is that C++
 can't have a method and a field with the same name.
 
 For now, the workaround is "don't do that".
 
 Later, we'd like to change the C++ compiler so we can have an
 attribute which will effectively rename one of the fields.  This
 attribute will also be useful when we want to represent fields with
 non-ASCII characters in their names (there might be another way to do
 that already, but I haven't studied UCN's enough to know if they are
 the right solution for us).
 
 Tom
>Unformatted:


             reply	other threads:[~2000-12-20 12:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-20 12:28 ashe [this message]
2003-05-14 10:43 giovannibajo

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=19991022233419.31153.qmail@sourceware.cygnus.com \
    --to=ashe@qms.com \
    --cc=java-gnats@sourceware.cygnus.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).