Re:The Sad State of C Strings
by ktRolster on Wednesday February 10, 2016 @04:26AM
(#11071585)
Of all the problems with C strings, the one mentioned in the article (inefficient strcat() function) is really small.
I think unicode support would be much more important, but not everyone agrees (for example, on embedded devices unicode support can be dead-weight). And adding to C without consensus leads to lousy decisions.
Re:The Sad State of C Strings
by reacweb on Wednesday February 10, 2016 @07:18AM
(#11072222)
I have already noticed some performance issue with strncpy (and big destination buffers) vs strlcpy. The two functions introduced in the article have the good complexity and seem to be more handy than usual api.
I think unicode support would be much more important, but not everyone agrees (for example, on embedded devices unicode support can be dead-weight). And adding to C without consensus leads to lousy decisions.