public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: jmr@ugcs.caltech.edu To: gcc-gnats@gcc.gnu.org Subject: java/8618: call to private constructor allowed for anonymous inner class Date: Fri, 22 Nov 2002 14:01:00 -0000 [thread overview] Message-ID: <20021118040143.7386.qmail@sources.redhat.com> (raw) >Number: 8618 >Category: java >Synopsis: call to private constructor allowed for anonymous inner class >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Sun Nov 17 20:06:01 PST 2002 >Closed-Date: >Last-Modified: >Originator: Jesse Rosenstock >Release: gcc version 3.2 20020903 (Red Hat Linux 8.0 3.2-7) >Organization: >Environment: >Description: Calls to private constructors are (incorrectly) allowed when creating an anonymous inner class. ; cat X.java public class X { public static void main(String[] args) { // new Y(); new Y() { }; // should be illegal } } ; cat Y.java public class Y { private Y() { } } ; gcj X.java Y.java --main=X gcj doesn't give an error, whereas Sun's javac does ; javac X.java X.java:4: Y() has private access in Y new Y() { }; ^ X.java:4: Y() has private access in Y new Y() { }; ^ 2 errors If you switch around which line is commented out in X.main, then gcj correctly gives an error: gcj X.java Y.java --main=X X.java:3: Can't access private constructor `Y.<init>' from `X'. new Y(); ^ 1 error >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2002-11-18 4:06 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20021118040143.7386.qmail@sources.redhat.com \ --to=jmr@ugcs.caltech.edu \ --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: linkBe 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).