public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/43241] std::tr1::regex is not fully implemented yet
Date: Wed, 14 Sep 2011 15:27:00 -0000	[thread overview]
Message-ID: <bug-43241-4-uV6vDroe8x@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-43241-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #10 from Jonathan Wakely <redi at gcc dot gnu.org> 2011-09-14 15:13:57 UTC ---
It's a known issue that std::regex is incomplete, as documented in the
libstdc++ manual.  If it makes you feel better file a bug, but it isn't going
to make any difference to anything. We know it's incomplete, we haven't
forgotten, we aren't waiting until someone notices before working on it.  As
Paolo says, contributions would be far more helpful than a bug report.


  parent reply	other threads:[~2011-09-14 15:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-43241-4@http.gcc.gnu.org/bugzilla/>
2011-09-14 15:04 ` sacolcor at provide dot net
2011-09-14 15:14 ` paolo.carlini at oracle dot com
2011-09-14 15:27 ` redi at gcc dot gnu.org [this message]
2011-09-14 15:37 ` redi at gcc dot gnu.org
2011-09-14 16:03 ` sacolcor at provide dot net
2010-03-03  0:17 [Bug libstdc++/43241] New: std::tr1::regex does not link pinskia at gcc dot gnu dot org
2010-03-03  0:21 ` [Bug libstdc++/43241] std::tr1::regex is not fully implemented yet pinskia at gcc dot gnu dot org
2010-03-03  1:16 ` paolo dot carlini at oracle dot com
2010-03-03 19:31 ` bangerth at gmail dot com
2010-03-03 19:31 ` bangerth at gmail dot com
2010-03-03 20:11 ` paolo dot carlini at oracle dot com
2010-03-03 20:14 ` pinskia at gcc dot gnu dot 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-43241-4-uV6vDroe8x@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).