public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fw at deneb dot enyo dot de" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug c++/23147] Missing declaration of static const members Date: Sat, 30 Jul 2005 15:11:00 -0000 [thread overview] Message-ID: <20050730134537.19893.qmail@sourceware.org> (raw) In-Reply-To: <20050730085712.23147.fw@deneb.enyo.de> ------- Additional Comments From fw at deneb dot enyo dot de 2005-07-30 13:45 ------- What about a GNU extension which would make this program well-formed? I think it's quite a common pattern, and a requirement to provide a definition would just increase object code size meaninglessly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23147
next prev parent reply other threads:[~2005-07-30 13:45 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-07-30 10:57 [Bug c++/23147] New: " fw at deneb dot enyo dot de 2005-07-30 13:45 ` [Bug c++/23147] " falk at debian dot org 2005-07-30 15:11 ` fw at deneb dot enyo dot de [this message] 2005-07-30 15:20 ` pinskia at gcc dot gnu dot org 2005-07-31 9:51 ` fw at deneb dot enyo dot de 2005-07-31 13:31 ` falk at debian dot org 2005-08-05 21:43 ` fw at deneb dot enyo dot de [not found] <bug-23147-192@http.gcc.gnu.org/bugzilla/> 2006-11-11 20:01 ` pinskia 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=20050730134537.19893.qmail@sourceware.org \ --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: 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).