public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Jason Merrill <jason@redhat.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6229: gcc 3.1 namespace lookup seems to fail
Date: Wed, 10 Apr 2002 04:36:00 -0000 [thread overview]
Message-ID: <20020410113606.29424.qmail@sources.redhat.com> (raw)
The following reply was made to PR c++/6229; it has been noted by GNATS.
From: Jason Merrill <jason@redhat.com>
To: "Peter Klotz" <peter.klotz@aon.at>
Cc: <gcc-gnats@gcc.gnu.org>
Subject: Re: c++/6229: gcc 3.1 namespace lookup seems to fail
Date: Wed, 10 Apr 2002 12:30:50 +0100
>>>>> "Peter" == Peter Klotz <peter.klotz@aon.at> writes:
> A final question remains: Why is the operator<< that takes a bool considered
> the best match for my function pointer (why not, for example, the one taking
> an int)?
Because there is a standard conversion from any pointer to bool, but not to
int.
Jason
next reply other threads:[~2002-04-10 11:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-10 4:36 Jason Merrill [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-04-08 7:26 peter.klotz
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=20020410113606.29424.qmail@sources.redhat.com \
--to=jason@redhat.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).