4 ms·
I feel like C has to go in the bucket of 'bad languages' these days, because it doesn't have sensible unicode support built in. But that doesn't mean you can't
by GlennS 8y ago
I feel like C has to go in the bucket of 'bad languages' these days, because it doesn't have sensible unicode support built in.
But that doesn't mean you can't have fun with it, or write good computer programs.
It just means that user inputted text is always going to be a pain.
- Nursie 8y agoTo be fair it doesn't really have strings 'built in' particularly well either. It directly manipulates memory patches, and the string support that is there is mostly a very simple abstraction on that. If you want support for unicode etc, there are libraries.
- solarkraft 8y agoBut then that brings you compatibility issues, overhead ...
- Nursie 8y agoIf you want to avoid development overhead, absolutely, C is a terrible language to pick. I'm not sure what you mean by compatibility issues in this context?
- solarkraft 8y agoI'm thinking about differen string representations used by different libraries. Is this not true?
- Nursie 8y agoHonestly all I've encountered default strings (and people shy away from those now) and LibICU stuff. I think ICU has become a defacto standard but I have been out of C for a few years. This tends to be important for strings you're going to show to the user (or input you gather from them), maybe most of the C in the world isn't aimed at interfaces like that...
- deleted 8y ago[deleted]
- jstimpfle 8y agoActually the best way to deal with unicode in almost all situations is to use UTF-8, and dealing with UTF-8 in C is trivial. For other encodings, well you need to decode explicitly (or just go for wide chars). Shouldn't come as a surprise, and not a big deal either.