public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "gnu-org at bignm dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libstdc++/63776] [C++11] Regex collate matching not working
Date: Tue, 20 Jan 2015 11:10:00 -0000 [thread overview]
Message-ID: <bug-63776-4-L8fA3NnXbP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63776-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63776
--- Comment #6 from Tom Straub <gnu-org at bignm dot com> ---
Hi Tim,
After banging my head against the wall looking for a solution to the C++11
UTF-8 support problems, I finally found what seems to be a great addition to my
project, which I think might be beneficial to GNU as well.
It is the UTF-8 CPP code. It is implemented as a header file, so there are no
linking issues involved. It seems to add all the functionality needed that
seems to be missing in GCC currently.
The project can be found at: http://sourceforge.net/projects/utfcpp/
It would certainly make implementation of the codecvt stuff less painful.
Best, Tom
next prev parent reply other threads:[~2015-01-20 11:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-07 18:39 [Bug c++/63776] New: " gnu-org at bignm dot com
2014-11-08 8:35 ` [Bug libstdc++/63776] " timshen at gcc dot gnu.org
2014-11-08 10:56 ` gnu-org at bignm dot com
2014-11-10 18:26 ` redi at gcc dot gnu.org
2015-01-20 11:05 ` gnu-org at bignm dot com
2015-01-20 11:10 ` gnu-org at bignm dot com [this message]
2015-01-20 13:08 ` redi at gcc dot gnu.org
2015-02-06 6:55 ` timshen at gcc dot gnu.org
2015-03-09 6:49 ` timshen 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-63776-4-L8fA3NnXbP@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).