public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "akim.demaille at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libstdc++/53631] [C++11] <regex> is unimplemented Date: Tue, 21 May 2013 09:00:00 -0000 [thread overview] Message-ID: <bug-53631-4-CbvitaeUPx@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-53631-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53631 --- Comment #11 from Akim Demaille <akim.demaille at gmail dot com> --- Sorry, I didn't mean to be harsh, and I did try to propose a solution. I can easily guess that there is no reason for it to be easy or even possible, but can't Boost people be asked if they'd contribute?
next prev parent reply other threads:[~2013-05-21 9:00 UTC|newest] Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-06-11 8:35 [Bug libstdc++/53631] New: " redi at gcc dot gnu.org 2012-06-11 8:37 ` [Bug libstdc++/53631] " redi at gcc dot gnu.org 2012-06-11 8:37 ` redi at gcc dot gnu.org 2012-06-11 8:37 ` redi at gcc dot gnu.org 2013-03-28 15:17 ` balakrishnan.erode at gmail dot com 2013-05-05 15:50 ` redi at gcc dot gnu.org 2013-05-21 8:09 ` akim.demaille at gmail dot com 2013-05-21 8:48 ` rleigh at debian dot org 2013-05-21 9:00 ` akim.demaille at gmail dot com [this message] 2013-05-21 9:03 ` redi at gcc dot gnu.org 2013-06-03 14:29 ` redi at gcc dot gnu.org 2013-06-23 2:10 ` zhaoxi.du at gmail dot com 2013-07-25 10:38 ` paolo.carlini at oracle dot com 2013-09-30 9:46 ` redi at gcc dot gnu.org 2013-10-01 15:38 ` timshen at gcc dot gnu.org 2014-06-10 17:22 ` redi at gcc dot gnu.org 2014-06-10 17:22 ` redi at gcc dot gnu.org 2014-07-20 23:16 ` 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-53631-4-CbvitaeUPx@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: linkBe 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).