public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "tromey at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/9369] wrong bytecode generated for static inner class with private constructor
Date: Fri, 13 May 2005 23:27:00 -0000	[thread overview]
Message-ID: <20050513232725.2984.qmail@sourceware.org> (raw)
In-Reply-To: <20030119181601.9369.jsturm@one-point.com>


------- Additional Comments From tromey at gcc dot gnu dot org  2005-05-13 23:27 -------
This no longer fails due to a change that went in as part of the fix
for PR 8618.  In particular, we now emit the 'Inner' constructor as
package-private, not private.

This is kind of a slacker approach to implementing accessors.
For constructors and static methods it probably has the desired
effect without doing harm, though I haven't considered it in great
detail.  For ordinary methods it might be a problem due to overriding.

This PR should only be marked as "fixed" if there is another PR for the
case of accessors for methods and fields.  Even then it isn't entirely
clear if this is more hack or more fix.



-- 


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


  parent reply	other threads:[~2005-05-13 23:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030119181601.9369.jsturm@one-point.com>
2005-02-10  0:28 ` pinskia at gcc dot gnu dot org
2005-05-12  2:03 ` pinskia at gcc dot gnu dot org
2005-05-13 23:27 ` tromey at gcc dot gnu dot org [this message]
2005-09-30 13:34 ` pinskia at gcc dot gnu dot org
     [not found] <bug-9369-447@http.gcc.gnu.org/bugzilla/>
2007-01-09 20:46 ` tromey 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=20050513232725.2984.qmail@sourceware.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).