public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "kariya_mitsuru at hotmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/64680] New: basic_regex::operator= does not reset flags
Date: Tue, 20 Jan 2015 02:53:00 -0000	[thread overview]
Message-ID: <bug-64680-4@http.gcc.gnu.org/bugzilla/> (raw)

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64680

            Bug ID: 64680
           Summary: basic_regex::operator= does not reset flags
           Product: gcc
           Version: 5.0
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: libstdc++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: kariya_mitsuru at hotmail dot com

Created attachment 34491
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=34491&action=edit
g++ -v

The sample code below should not throw a regex_error.

========================= sample code =========================
#include <regex>

int main()
{
    std::regex re("[[:alnum:]]", std::regex_constants::basic);
    re = "\\w+";
}
===============================================================
cf. http://melpon.org/wandbox/permlink/lrD2Ia4urIPVgakK


According to the C++11 standard 28.8.3[re.regex.assign], operator=(const charT*
ptr) is equivalent to assign(ptr), and assign(ptr) calls assign(const char*
ptr, flag_type f = regex_constants::ECMAScript).

Since "\\w+" is a valid ECMAScript syntax, the sample code above should end
normally.


             reply	other threads:[~2015-01-20  2:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-20  2:53 kariya_mitsuru at hotmail dot com [this message]
2015-01-22  5:07 ` [Bug libstdc++/64680] " timshen at gcc dot gnu.org
2015-02-03  9:02 ` timshen at gcc dot gnu.org
2015-03-09  6:52 ` timshen at gcc dot gnu.org
2023-07-20 11:45 ` 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-64680-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).