Future of musl locale/strerror(). In LC_MESSAGES=C, strerror(ENOENT) = ?
-
Show this thread
-
Context for this lovely bikeshed here: http://www.openwall.com/lists/musl/2018/03/05/2 …
1 reply 0 retweets 0 likesShow this thread -
And would you change answer if I told you option 1 makes libc 1k bigger, 2 makes it 1k smaller?
2 replies 0 retweets 1 likeShow this thread -
Replying to @RichFelker
If including most localizations only costs ~1-2k that seems like a fairly small price pay for better internationalization support out of the box. Save a lot of developer time, and concern. But I guess embedded folks maybe against it.
1 reply 0 retweets 0 likes -
Replying to @valarauca1
Obviously things are oversimplified in a tweet. The question is whether to keep English-phrase error msgs in C locale or use the E* codes (more 'language-agnostic').
2 replies 0 retweets 0 likes
In the former case, it costs more size to make the translation framework clean. In the latter, making the translation framework clean also makes it smaller (and you can have English-phrase error msgs still in "en" locale, just not "C").
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.