public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: mjrauhal@cc.helsinki.fi To: gcc-gnats@gcc.gnu.org Subject: java/9884: gcj compiles code that uses non-static inner classes from static context Date: Fri, 28 Feb 2003 00:06:00 -0000 [thread overview] Message-ID: <20030228000308.17934.qmail@sources.redhat.com> (raw) >Number: 9884 >Category: java >Synopsis: gcj compiles code that uses non-static inner classes from static context >Confidential: no >Severity: non-critical >Priority: medium >Responsible: unassigned >State: open >Class: accepts-illegal >Submitter-Id: net >Arrival-Date: Fri Feb 28 00:06:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: Mikko Rauhala >Release: 3.2.3 >Organization: >Environment: Debian GNU/Linux (unstable), recently upgraded (gcj-3.2 package version 3.2.3-0pre2). >Description: gcj accepts code that uses non-static inner classes from static context. This is AFAIK illegal in Java, and Sun's compiler rejects it with the message: InnerClassBug.java:11: non-static variable this cannot be referenced from a static context InnerClass theObjectThatShouldNotBe = new InnerClass(); ^ 1 error >How-To-Repeat: Compile the following snippet of code and run it (command: "gcj-wrapper-3.2 InnerClassBug.java && gij-3.2 InnerClassBug"): public class InnerClassBug { class InnerClass { InnerClass() { } void sayHi() { System.out.println("Hi, I'm the Object that Should Not Be."); } } public static void main(String args[]) { InnerClass theObjectThatShouldNotBe = new InnerClass(); theObjectThatShouldNotBe.sayHi(); } } >Fix: Give an error message when that kind of thing is attempted. >Release-Note: >Audit-Trail: >Unformatted:
reply other threads:[~2003-02-28 0: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=20030228000308.17934.qmail@sources.redhat.com \ --to=mjrauhal@cc.helsinki.fi \ --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).