public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aph@gcc.gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug java/8626] warn for non-static references to static members
Date: Thu, 22 May 2003 17:20:00 -0000 [thread overview]
Message-ID: <20030522171610.18510.qmail@sources.redhat.com> (raw)
PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=8626
------- Additional Comments From aph@gcc.gnu.org 2003-05-22 17:16 -------
Why should anyone want such a warning? Surely lots of code
references static objects in non-static contexts.
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next reply other threads:[~2003-05-22 17:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-22 17:20 aph@gcc.gnu.org [this message]
[not found] <20021118131601.8626.tromey@redhat.com>
2003-05-25 23:13 ` pinskia@physics.uc.edu
2003-06-17 1:41 ` tromey@redhat.com
2003-06-30 14:14 ` pinskia at physics dot uc dot edu
[not found] <20021118131601.8626.tromey@gcc.gnu.org>
2004-02-14 19:42 ` pinskia at gcc dot gnu dot org
[not found] <bug-8626-360@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=20030522171610.18510.qmail@sources.redhat.com \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@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).