public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: nathan@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org,
mike@thetroubleshooters.dk, mn@onair.dk, nobody@gcc.gnu.org
Subject: Re: c++/10680: Inlining in inheritance seems broken.
Date: Thu, 08 May 2003 13:51:00 -0000 [thread overview]
Message-ID: <20030508135137.29123.qmail@sources.redhat.com> (raw)
Synopsis: Inlining in inheritance seems broken.
State-Changed-From-To: open->closed
State-Changed-By: nathan
State-Changed-When: Thu May 8 13:51:37 2003
State-Changed-Why:
not a bug. [7.1.2]/4 says 'an inline funcxtion shall be defined in every translation unit in which it is used ...'
You have used it in translation unit b.cpp, but it is not defined nor declared inline within that TU.
http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10680
next reply other threads:[~2003-05-08 13:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-08 13:51 nathan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-09 10:26 Michael Nielsen
2003-05-08 13:16 mn
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=20030508135137.29123.qmail@sources.redhat.com \
--to=nathan@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
--cc=gcc-gnats@gcc.gnu.org \
--cc=gcc-prs@gcc.gnu.org \
--cc=mike@thetroubleshooters.dk \
--cc=mn@onair.dk \
--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).