public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: bkoz@gcc.gnu.org
To: bkoz@gcc.gnu.org, dmuell@gmx.net, gcc-bugs@gcc.gnu.org,
	gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2989: ambiguous overload of strcpy when including iostream
Date: Fri, 08 Jun 2001 16:07:00 -0000	[thread overview]
Message-ID: <20010608230751.14539.qmail@sourceware.cygnus.com> (raw)

Synopsis: ambiguous overload of strcpy when including iostream

State-Changed-From-To: analyzed->feedback
State-Changed-By: bkoz
State-Changed-When: Fri Jun  8 16:07:50 2001
State-Changed-Why:
    Should be fixed with:
    
    2001-06-08  Benjamin Kosnik  <bkoz@redhat.com>
    
    	libstdc++/2989
    	libstdc++/2992
    	* include/std/*: Add copyright notice.
    	* include/c_std/bits/*: Use using statements instead of extern "C".
    	* include/c_std/bits/std_cmath.h: Don't overload double versions
    	of math functions with __buitin versions, use global version to
    	prevent ambiguities. Remove define hacks.
    	* include/c_std/bits/std_cwchar.h: Using declarations for "C"
    	functions that have changed signatures and std::
    	declarations. Remove define hacks.
    	* include/c_std/bits/std_cwchar.h: Same, plus remove ambiguous
    	__builtins in std::. Remove define hacks.
    	* testsuite/17_intro/headers_c.cc: Add tests.
    	* testsuite/17_intro/headers_c++.cc: Add test.
    
    
    I'm checking this into the branch right now.
    
    thanks!
    
    -benjamin

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view&pr=2989&database=gcc


             reply	other threads:[~2001-06-08 16:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-08 16:07 bkoz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-06-09 23:50 bkoz
2001-06-09 10:56 Benjamin Kosnik
2001-06-07 15:20 mmitchel

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=20010608230751.14539.qmail@sourceware.cygnus.com \
    --to=bkoz@gcc.gnu.org \
    --cc=dmuell@gmx.net \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-prs@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).