public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "luto at mit dot edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/53561] New: [c++0x] regex_replace is missing overloads
Date: Sat, 02 Jun 2012 02:06:00 -0000	[thread overview]
Message-ID: <bug-53561-4@http.gcc.gnu.org/bugzilla/> (raw)

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53561

             Bug #: 53561
           Summary: [c++0x] regex_replace is missing overloads
    Classification: Unclassified
           Product: gcc
           Version: 4.8.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
        AssignedTo: unassigned@gcc.gnu.org
        ReportedBy: luto@mit.edu


[re.alg.replace] says:

template <class traits, class charT, class ST, class SA>
basic_string<charT, ST, SA>
regex_replace(const basic_string<charT, ST, SA>& s,
const basic_regex<charT, traits>& e,
const charT* fmt,
regex_constants::match_flag_type flags =
regex_constants::match_default);

This doesn't compile, though:

#include <string>
#include <regex>

int main()
{
  std::regex_replace<std::regex_traits<char>, char>(std::string("x"),
std::regex("x"), "y");  // works

  std::regex_replace(std::string("x"), std::regex("x"), "y");  // fails

  return 0;
}

The string,regex,string,flags overload doesn't work because the arguments
aren't an exact match.


             reply	other threads:[~2012-06-02  2:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-02  2:06 luto at mit dot edu [this message]
2012-06-02  2:09 ` [Bug libstdc++/53561] " luto at mit dot edu
2012-07-21 17:52 ` vallentin at icir dot org
2012-07-21 18:00 ` redi at gcc dot gnu.org
2023-07-20 11:26 ` redi at gcc dot gnu.org

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=bug-53561-4@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).