public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Martin Sebor <sebor@roguewave.com>
To: jason@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/7824: Temporary ostream doesn't work properly with operator<< and const char*
Date: Wed, 06 Nov 2002 09:56:00 -0000	[thread overview]
Message-ID: <20021106175603.31631.qmail@sources.redhat.com> (raw)

The following reply was made to PR libstdc++/7824; it has been noted by GNATS.

From: Martin Sebor <sebor@roguewave.com>
To: bkoz@gcc.gnu.org,  gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: libstdc++/7824: Temporary ostream doesn't work properly with
 operator<< and const char*
Date: Wed, 06 Nov 2002 10:52:45 -0700

 bkoz@gcc.gnu.org wrote:
 > Synopsis: Temporary ostream doesn't work properly with operator<< and const char*
 > 
 > Responsible-Changed-From-To: unassigned->jason
 > Responsible-Changed-By: bkoz
 > Responsible-Changed-When: Wed Nov  6 08:43:44 2002
 > Responsible-Changed-Why:
 >     Jason, can you take a look at this? If not, maybe Nathan? I think this is an issue with overload resolution and temporaries. Seems odd.
 
 That's the correct behavior. The char* non-member inserter takes
 a non-const reference, so it's not a viable match. The void*
 inserter is a member, so it is called for the unnamed temporary
 (rvalue). We got the same report a while ago :)
 
 Regards
 Martin
 


             reply	other threads:[~2002-11-06 17:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  9:56 Martin Sebor [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-11-06 11:36 Benjamin Kosnik
2002-11-06 11:31 bkoz
2002-11-06  8:43 bkoz

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=20021106175603.31631.qmail@sources.redhat.com \
    --to=sebor@roguewave.com \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=jason@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).