public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: pimlott@idiomtech.com To: gcc-gnats@gcc.gnu.org Subject: java/3635: "empty declaration" warning too broad Date: Tue, 10 Jul 2001 09:16:00 -0000 [thread overview] Message-ID: <20010710160655.24191.qmail@sourceware.cygnus.com> (raw) >Number: 3635 >Category: java >Synopsis: "empty declaration" warning too broad >Confidential: no >Severity: non-critical >Priority: low >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Jul 10 09:16:00 PDT 2001 >Closed-Date: >Last-Modified: >Originator: Andrew Pimlott >Release: gcc version 3.0 (Debian) >Organization: >Environment: Debian GNU/Linux "testing" >Description: I am fairly new to java and gcj, and I am confused by the warning generated by class Test { void foo() { ; } } % gcj-3.0 -C -Wall Test.java Test.java:3: warning: An empty declaration is a deprecated feature that +should not be used. void foo() { ; } ^ 1 warning >How-To-Repeat: See code in description. >Fix: >Release-Note: >Audit-Trail: >Unformatted: >From what I can find (mainly, the bug report gcj/295), this warning is supposed to be about semicolons after inner classes. The JLS second edition says nothing bad about empty statements, so I hope this is a mistake. [This was originally sent to java@gcc.gnu.org with subject "empty declaration deprecated". Alexandre Petit-Bianco <apbianco@cygnus.com> replied confirming that it is probably a bug.]
next reply other threads:[~2001-07-10 9:16 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2001-07-10 9:16 pimlott [this message] 2001-07-12 15:47 apbianco 2002-01-04 18:56 rodrigc
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=20010710160655.24191.qmail@sourceware.cygnus.com \ --to=pimlott@idiomtech.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: 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).