From: Tyson Whitehead <twhitehe@uwo.ca>
To: gcc@gcc.gnu.org
Cc: Wolfgang Bangerth <bangerth@ices.utexas.edu>,
Gabriel Dos Reis <gdr@cs.tamu.edu>
Subject: Re: Template Template Matching Problem on Defaults (old g++ extension induced problem -- bug 9737)
Date: Mon, 20 Sep 2004 19:04:00 -0000 [thread overview]
Message-ID: <200409201422.17316.twhitehe@uwo.ca> (raw)
In-Reply-To: <Pine.LNX.4.44.0409201104540.13253-100000@terra.ices.utexas.edu>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On September 20, 2004 12:11 pm, Wolfgang Bangerth wrote:
> That isn't the point. The reason was so that people can match
> std::vector<int>
> std::set<int>
> ...
> etc to template template parameters with only one template argument,
> despite the fact that these classes have more than just one, and possibly
> different numbers of template arguments, all of which except for the first
> have default arguments.
On September 20, 2004 12:52 pm, Gabriel Dos Reis wrote:
> The Core group clarified the point saying that template parameters
> and default arguments are intended to be treated the same way as
> function parameters and default arguments.
>
> With template aliases coming in, I think this extension can go away.
Thanks all, for the clarification.
It probably moot for this case, as it sounds like this non-core extension will
probably be going out with template alias coming in, but shouldn't g++
extensions that provide extra candidates over the C++ standard be made to
match less strongly then C++ standard candidates to ensure g++ specific
ambiguities aren't introduced into perfectly valid code (such as that in the
original email)?
- -T
- --
Tyson Whitehead (-twhitehe at uwo.ca -- WSC-)
Computer Engineer Dept. of Applied Mathematics,
Graduate Student- Applied Mathematics University of Western Ontario,
GnuPG Key ID# 0x8A2AB5D8 London, Ontario, Canada
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
iD8DBQFBTx/XRXbLmIoqtdgRAjM+AKDtkEIRgvQQ71GuELB2BC62I9gRZgCfeFOB
WqOklFtxnqAJjA1M/3ii+rs=
=uH3W
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-09-20 18:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-20 17:47 Wolfgang Bangerth
2004-09-20 18:22 ` Gabriel Dos Reis
2004-09-20 19:04 ` Tyson Whitehead [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-20 7:14 Tyson Whitehead
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=200409201422.17316.twhitehe@uwo.ca \
--to=twhitehe@uwo.ca \
--cc=bangerth@ices.utexas.edu \
--cc=gcc@gcc.gnu.org \
--cc=gdr@cs.tamu.edu \
/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).