public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/10086: static const int unresolved in ? : construct
Date: Sat, 15 Mar 2003 17:06:00 -0000	[thread overview]
Message-ID: <20030315170602.20850.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/10086; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: Chris Kappler <chrisk@mysticlabs.com>
Cc: gcc-bugs@gcc.gnu.org, <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/10086: static const int unresolved in ? : construct
Date: Sat, 15 Mar 2003 11:03:22 -0600 (CST)

 > I do not agree. 
 
 That doesn't make it right. The standard says that you need to have 
 definitions of static variables like
   const int Base::A;
 and it allows the compiler to make use of these variables without using 
 the provided constant initializers. Just because it uses them in one 
 context and not in another doesn't mean you should rely on that.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth             email:            bangerth@ticam.utexas.edu
                               www: http://www.ticam.utexas.edu/~bangerth/
 
 


             reply	other threads:[~2003-03-15 17:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-15 17:06 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-03-16  9:36 Gabriel Dos Reis
2003-03-16  1:06 Giovanni Bajo
2003-03-15 16:56 Chris Kappler
2003-03-14 22:33 bangerth
2003-03-14 21:36 chrisk

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=20030315170602.20850.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).