str

Most of the code I write has a spec of input and output being some form of text. Still, I tend to write that in languages that have safe string handling and drop into C only when the profiler indicates that's useful. When handling strings in C, it's useful to use the string functions from glib or pull in one of the specifically safe string handling libraries and not use any C stdlib functions for strings at all. There are a number of C strings libraries safer to use than the standard library, and many of them are simpler, more feature-rich, or both. * https://github.com/intel/safestringlib (MIT licensed) * https://github.com/rurban/safeclib (MITish) * https://github.com/mpedrero/safeString (MIT licensed) * https://github.com/antirez/sds (BSD 2-clause, and gives you dynamic strings) * https://github.com/maxim2266/str (BSD 3-clause) * https

There is some support for reading a string as an encoded in the current program locale. See: https://github.com/maxim2266/str#unicode-support

oof bit packing to save a single bit? https://github.com/maxim2266/str/blob/f4e84657b23977ab3c5cd7... seems unlikely to matter if you have a bunch of strings flying around... two features I'd love to see implemented: - wrapping thread safe tokenization using strtok_r so it's pleasant to tokenize a string - sprintf-like formatting anything that improves string handling in C is doing God's work