* About u8filebuf u16filebuf u32filebuf, undocumented features?
@ 2020-12-06 10:09 sotrdg sotrdg
0 siblings, 0 replies; only message in thread
From: sotrdg sotrdg @ 2020-12-06 10:09 UTC (permalink / raw)
To: libstdc++
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>
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-12-06 10:09 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-12-06 10:09 About u8filebuf u16filebuf u32filebuf, undocumented features? sotrdg sotrdg
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).