public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "daniel.kruegler at googlemail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/52036] C++11 allows template parameters to have internal linkage
Date: Sun, 29 Jan 2012 18:15:00 -0000 [thread overview]
Message-ID: <bug-52036-4-vBN0IWxmMl@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-52036-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=52036
--- Comment #4 from Daniel Krügler <daniel.kruegler at googlemail dot com> 2012-01-29 17:28:14 UTC ---
(In reply to comment #3)
> However compilation still fails if pi is given internal linkage by declaring it > static, i.e.
>
> int main()
> {
> static constexpr float pi = 3.14;
>
> Or even:
>
> namespace {
> static constexpr float pi = 3.14;
> }
I agree that both examples should work and that the lack of that is a bug when
compiled in C++11 mode. Paolo, this bug should be reopened.
next prev parent reply other threads:[~2012-01-29 17:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 8:52 [Bug c++/52036] New: " benjamin at benkay dot net
2012-01-29 14:33 ` [Bug c++/52036] " daniel.kruegler at googlemail dot com
2012-01-29 14:42 ` paolo.carlini at oracle dot com
2012-01-29 17:27 ` benjamin at benkay dot net
2012-01-29 18:15 ` daniel.kruegler at googlemail dot com [this message]
2012-01-29 19:01 ` paolo.carlini at oracle dot com
2012-01-29 22:51 ` redi at gcc dot gnu.org
2012-01-30 20:19 ` daniel.kruegler at googlemail dot com
2013-08-09 23:54 ` richard-gccbugzilla at metafoo dot co.uk
2014-03-03 22:57 ` mizvekov at gmail dot com
2015-03-23 7:52 ` oakad at yahoo dot com
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=bug-52036-4-vBN0IWxmMl@http.gcc.gnu.org/bugzilla/ \
--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).