* Why there are no macro to access the name of current exec-charset and fwide-exec-charset??????
@ 2020-11-25 22:14 sotrdg sotrdg
0 siblings, 0 replies; only message in thread
From: sotrdg sotrdg @ 2020-11-25 22:14 UTC (permalink / raw)
To: gcc, jakub
I have to make filename work correctly under none UTF-8 exec charset. Do not tell me to use locale since locale is not thread-safe and configure locale is a huge issue.
I do not use any C stdio or C++ iostream facilities since I create my own I/O library from scratch. However, this is something I would like to deal with it correctly since none of these libc library does the right thing, they all assume exec-charset is UTF-8 and that just creates format string vulnerabilities silently.
If you guys could not correctly support this feature, please just remove that toggle, just like removing trigraph. Clang does not support none UTF-8 exec-charset and no one complains about it.
Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2020-11-25 22:14 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-11-25 22:14 Why there are no macro to access the name of current exec-charset and fwide-exec-charset?????? 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).