Glib sux
Thanks for the info.
When it comes to string-operations, I avoid the glibc-string-headers like the plague and rather refrain to writing my own string-functions which are almost always 1.5-2x faster than the glibc-counterpart (mostly, because you can design your functions for your current needs and strip a lot).
Suckless.org has a good reason to list GlibC as a library considered harmful (http://suckless.org/sucks) and we should all stay away from it if possible and make up our own mind on how to deal with those things effectively, without being infected with C++ STL-crap. (Call me a C++-Hater, that's what I am ).
Originally posted by gens
View Post
When it comes to string-operations, I avoid the glibc-string-headers like the plague and rather refrain to writing my own string-functions which are almost always 1.5-2x faster than the glibc-counterpart (mostly, because you can design your functions for your current needs and strip a lot).
Suckless.org has a good reason to list GlibC as a library considered harmful (http://suckless.org/sucks) and we should all stay away from it if possible and make up our own mind on how to deal with those things effectively, without being infected with C++ STL-crap. (Call me a C++-Hater, that's what I am ).
Comment