From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Ivo Doko <ivo.doko@gmail.com>
Cc: gcc-help <gcc-help@gcc.gnu.org>
Subject: Re: A possible bug
Date: Tue, 07 Oct 2014 10:45:00 -0000 [thread overview]
Message-ID: <CAH6eHdRFhyJiYtU5RwVo+PXQORFZ5ijS3yxZrNAhqY1BQgraeQ@mail.gmail.com> (raw)
In-Reply-To: <5433AF43.9070102@gmail.com>
On 7 October 2014 10:15, Ivo Doko wrote:
> As far as I can
> see, the problem should happen only if static const(expr) variables are
> accessed outside the class/struct body.
No, that's completely irrelevant. I don't know how you would reach
that conclusion form the reference I gave, which says nothing of the
sort.
What matters is whether you use the variable in such a way that the
compiler needs a definition of the variable, rather than just needing
to know its value.
next prev parent reply other threads:[~2014-10-07 10:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-07 5:01 Ivo Doko
2014-10-07 8:37 ` Ivo Doko
2014-10-07 8:57 ` Jonathan Wakely
2014-10-07 9:16 ` Ivo Doko
2014-10-07 10:45 ` Jonathan Wakely [this message]
2014-10-07 9:28 ` Ivo Doko
2014-10-07 10:48 ` Jonathan Wakely
2014-10-07 11:48 ` Ivo Doko
2014-10-07 11:49 ` Ivo Doko
2014-10-07 12:25 ` Andrew Haley
2014-10-07 13:55 ` Ivo Doko
2014-10-07 12:25 ` Jonathan Wakely
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=CAH6eHdRFhyJiYtU5RwVo+PXQORFZ5ijS3yxZrNAhqY1BQgraeQ@mail.gmail.com \
--to=jwakely.gcc@gmail.com \
--cc=gcc-help@gcc.gnu.org \
--cc=ivo.doko@gmail.com \
/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).