public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: "John Ratliff" <webmaster@technoplaza.net>
Cc: <gcc-help@gcc.gnu.org>
Subject: Re: C++ static integer class constants...
Date: Mon, 17 Oct 2005 19:17:00 -0000	[thread overview]
Message-ID: <873bn0rm24.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <87oe5pb5dp.fsf@totally-fudged-out-message-id> (John Ratliff's message of "Sun, 16 Oct 2005 14:53:05 -0500")

* John Ratliff:

> On comp.lang.c++, Victor Bazarov says my example program is well-formed
> standard C++ according to the ISO C++ standard.
>
> "Since their address is never taken, the 'foo::A' and 'foo::B' are, in
> fact, compile-time constant expressions that do not require storage.
> The objects, therefore, don't need to be defined outside of the class
> definition.

This analysis argues from the implementation, not from the standard.

The standard requires that you provide a definition if you use the
constant in a place which does not *require* a constant expression.
In other words,

  int foo[Class::static_const_member];

is fine without a definition, but

  int bar = Class::static_const_member;

is not.

It's strange and smells like a mistake in the standard.

       reply	other threads:[~2005-10-17 19:17 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87oe5pb5dp.fsf@totally-fudged-out-message-id>
2005-10-17 19:17 ` Florian Weimer [this message]
2005-10-18  6:19   ` John Ratliff
2005-10-18  6:19   ` John Ratliff
     [not found] <0IOJ0024ULK8BF@emroute1.cind.ornl.gov>
2005-10-18 12:26 ` Ernest L. Williams Jr.
     [not found] <200510160743.j9G7hVoa010304@inbound-smtp-1.corp.adobe.com>
2005-10-17 12:05 ` John Love-Jensen
2005-10-17 17:50   ` John Ratliff
2005-10-17 17:50   ` John Ratliff
     [not found]   ` <4353e481.0829b6d6.64bd.18a4SMTPIN_ADDED@mx.gmail.com>
2005-10-17 18:07     ` corey taylor
2005-10-17 20:04       ` John Ratliff
2005-10-17 20:04       ` John Ratliff
     [not found] <20051016195314.7EFB824AEF5@lax-gw02.mroute.net>
2005-10-17  9:09 ` Nathan Sidwell
2005-10-17 19:21   ` Florian Weimer
     [not found] <20051016200125.C061F13137C@arvo.suso.org>
2005-10-16 21:36 ` John Ratliff
2005-10-16 21:36 ` John Ratliff
2005-10-16 15:26 Ryan Mansfield
2005-10-16 16:16 ` John Ratliff
2005-10-16 16:16 ` John Ratliff
2005-10-16 16:42 ` John Ratliff
2005-10-16 16:42 ` John Ratliff
     [not found] ` <43528310.03f34613.6a05.0e40SMTPIN_ADDED@mx.gmail.com>
2005-10-16 17:43   ` Alex J. Dam
     [not found]     ` <4352a3b2.42389977.3b5e.60fdSMTPIN_ADDED@mx.gmail.com>
2005-10-16 19:29       ` Alex J. Dam
2005-10-16 19:53         ` John Ratliff
2005-10-16 19:53         ` John Ratliff
2005-10-16 19:45     ` John Ratliff
2005-10-16 19:45     ` John Ratliff
     [not found] <435202e6.3d759d8f.4550.fffff1e6SMTPIN_ADDED@mx.gmail.com>
2005-10-16 14:50 ` Alex J. Dam
2005-10-17 19:13   ` Florian Weimer
  -- strict thread matches above, loose matches on Subject: below --
2005-10-16  7:35 John Ratliff
2005-10-16  7:35 John Ratliff

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=873bn0rm24.fsf@mid.deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=gcc-help@gcc.gnu.org \
    --cc=webmaster@technoplaza.net \
    /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).