From: Jonathan Wakely <jwakely.gcc@gmail.com>
To: Gerald Pfeifer <gerald@pfeifer.com>
Cc: Sandra Loosemore <sandra@codesourcery.com>,
"gcc@gcc.gnu.org" <gcc@gcc.gnu.org>
Subject: Re: Doc question: is "templatized" a word?
Date: Sat, 11 Feb 2017 13:21:00 -0000 [thread overview]
Message-ID: <CAH6eHdRZwgzguxjt1Ab=vbvtphkx6DxaF+_45F1G3RX3D_Bvew@mail.gmail.com> (raw)
In-Reply-To: <alpine.LSU.2.20.1702110947200.2253@anthias.pfeifer.com>
On 11 February 2017 at 08:48, Gerald Pfeifer wrote:
> On Fri, 10 Feb 2017, Sandra Loosemore wrote:
>> The documentation for -Wno-non-template-friend refers to "non-templatized
>> friend functions" and "templatized functions". I don't see the term
>> "templatized" used anywhere in the C++ standard. This paragraph also uses
>> "nontemplate function", which I assume refers to the same thing the C++
>> standard spells "non-template function". So does "non-templatized function"
>> also mean "non-template function"? Or does it have some other meaning?
>
> I would avoid "templatized" and believe "non-template function" is
> more appropriate in your example.
Yes,
s/non-templatized/non-template/
s/nontemplate/non-template/
s/templatized function/function template/
But I wonder if that warning is even useful nowadays. The example of
"friend foo(int);" is bogus and is correctly rejected:
fr.cc:2:17: error: ISO C++ forbids declaration of ‘foo’ with no type
[-fpermissive]
friend foo(int);
^
next prev parent reply other threads:[~2017-02-11 13:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-11 4:11 Sandra Loosemore
2017-02-11 8:48 ` Gerald Pfeifer
2017-02-11 13:21 ` Jonathan Wakely [this message]
2017-02-11 20:36 ` Sandra Loosemore
2017-02-11 21:20 ` Jonathan Wakely
2017-02-15 15:53 ` Jason Merrill
2017-02-15 18:57 ` Jonathan Wakely
2017-02-15 20:17 ` Jason Merrill
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='CAH6eHdRZwgzguxjt1Ab=vbvtphkx6DxaF+_45F1G3RX3D_Bvew@mail.gmail.com' \
--to=jwakely.gcc@gmail.com \
--cc=gcc@gcc.gnu.org \
--cc=gerald@pfeifer.com \
--cc=sandra@codesourcery.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).