Thread with 4 posts
jump to expanded post
today I learned that almost every C string (char*) function has a wide string (wchar_t*) equivalent
today I am also thankful that Rust has generics: https://github.com/hikari-no-yume/touchHLE/commit/a82b61095973ef678ceaf655e90524dd4202dde7
bold of the c committee to think null-terminated strings should survive into the unicode age. lol
@hikari Depends what you are coding for. If you are writing network protocols you don’t want wide strings! When using Kotlin or Java for such uses I am always converting back in to utf-8 strings in byte arrays and the reverse. In C wide strings were a bolt on for UTF-16.
@hikari In my development I rarely use wide strings when I am using C (as its device drivers, networking, OS level) and I use other languages for more user oriented code.