From: sotrdg sotrdg <euloanty@live.com>
To: libstdc++ <libstdc++@gcc.gnu.org>
Subject: About u8filebuf u16filebuf u32filebuf, undocumented features?
Date: Sun, 6 Dec 2020 10:09:44 +0000 [thread overview]
Message-ID: <CH2PR02MB6522F40B099F4ADE319A89EEB2CF0@CH2PR02MB6522.namprd02.prod.outlook.com> (raw)
Did I find out a hidden feature inside libstdc++?
i tried to use
std::basic_filebuf<char8_t>
std::basic_filebuf<char16_t>
std::basic_filebuf<char32_t>
It does not look like C++ fstream supports char8_t char16_t char32_t.
However, my fast_io library supports formatted i/o for char8_t char16_t and char32_t. I tried them with fast_io's facilitiea and they work perfectly fine, with codecvt to locale encoding char set.
https://github.com/expnkx/fast_io/blob/f6efd9dc1c3f4915e0e9ee48d884c682157a9121/include/fast_io_legacy_impl/cpp/filebuf_file.h#L173
Are they undocumented standard library features?
Should i use them without worrying about some other standard library implementations do not support them?
Get Outlook for Android<https://aka.ms/ghei36>
reply other threads:[~2020-12-06 10:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CH2PR02MB6522F40B099F4ADE319A89EEB2CF0@CH2PR02MB6522.namprd02.prod.outlook.com \
--to=euloanty@live.com \
--cc=libstdc++@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).