public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Philippe A. Bouchard" <philippeb@videotron.ca>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6030: ...
Date: Mon, 13 Jan 2003 05:16:00 -0000 [thread overview]
Message-ID: <20030113051602.25332.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6030; it has been noted by GNATS.
>From philippeb@videotron.ca Mon Jan 13 01:09:28 2003
From: "Philippe A. Bouchard" <philippeb@videotron.ca>
To: neroden@twcny.rr.com, gcc-gnats@gcc.gnu.org, gcc-bugs@gcc.gnu.org,
nobody@gcc.gnu.org
Cc:
Subject: Re: c++/6030: ...
Date: Mon, 13 Jan 2003 00:11:40 -0500
----- Original Message -----
From: "Nathanael Nerode" <neroden@twcny.rr.com>
To: <philippeb@videotron.ca>; <gcc-gnats@gcc.gnu.org>;
<gcc-bugs@gcc.gnu.org>; <nobody@gcc.gnu.org>
Sent: Saturday, January 11, 2003 6:57 PM
Subject: Re: c++/6030: ...
> I'm a little confused by all this, but note that the following seems to
work:
> --
[...]
> int main()
> {
> foo<int, 9>();
> foo<blah_fn, b>();
> }
[...]
> int main()
> {
> foo<int, 9>();
> foo<int (*) (void), b>();
> }
> --
>
> This seems like a sufficient workaround for most any purpose. It also
works
> if you replace the * by &.
>
> And it leaves me wondering about the validity of the original. :-)
Yes, you're right: non-type non-reference template parameters cannot be of
function type (14.1.3 - .4). But I would suggest clarifying the error
report: "no matching function for call to foo()" with some "invalid non-type
type".
Thanks,
Philippe A. Bouchard
next reply other threads:[~2003-01-13 5:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 5:16 Philippe A. Bouchard [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-12 0:06 c++/6030: Nathanael Nerode
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=20030113051602.25332.qmail@sources.redhat.com \
--to=philippeb@videotron.ca \
--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).