public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "spamjunk" <spamjunk@stny.rr.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6945: A static constant that is initialize inline is not create if only a temperary is used
Date: Fri, 07 Jun 2002 14:36:00 -0000 [thread overview]
Message-ID: <20020607213602.11762.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6945; it has been noted by GNATS.
From: "spamjunk" <spamjunk@stny.rr.com>
To: <lerdsuwa@gcc.gnu.org>, <gcc-bugs@gcc.gnu.org>, <gcc-prs@gcc.gnu.org>,
<nobody@gcc.gnu.org>, <spamjunk@stny.rr.com>, <gcc-gnats@gcc.gnu.org>
Cc:
Subject: Re: c++/6945: A static constant that is initialize inline is not create if only a temperary is used
Date: Fri, 7 Jun 2002 17:27:50 -0400
Not true. You can't do that when its initialized inline in the class, the
compiler will tell its that its defined twice.
----- Original Message -----
From: <lerdsuwa@gcc.gnu.org>
To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <nobody@gcc.gnu.org>;
<spamjunk@stny.rr.com>
Sent: Friday, June 07, 2002 10:12 AM
Subject: Re: c++/6945: A static constant that is initialize inline is not
create if only a temperary is used
> Synopsis: A static constant that is initialize inline is not create if
only a temperary is used
>
> State-Changed-From-To: open->closed
> State-Changed-By: lerdsuwa
> State-Changed-When: Fri Jun 7 07:12:16 2002
> State-Changed-Why:
> Not a bug. You have to define 'i' by adding
> const int T::i;
> after the definition of class T.
>
>
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&p
r=6945
>
next reply other threads:[~2002-06-07 21:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-07 14:36 spamjunk [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-06-07 14:56 Phil Edwards
2002-06-07 7:12 lerdsuwa
2002-06-06 6:36 spamjunk
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=20020607213602.11762.qmail@sources.redhat.com \
--to=spamjunk@stny.rr.com \
--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).