Your argument ignores two simple and completely obvious facts:
First, there are many, many existing usage instances of unsafe string handling functions that can be greatly improved through a trivial conversion to strlcpy/strlcat. It is silly to expect them to all be completely rewritten to use unbounded strings, which can have their own problems that fixed length strings do not (potential memory consumption DoS, integer overflow, etc.)
Second, there are many, many cases where you want or need a fixed length string. Lots of network protocols, file formats and system interfaces require them, so why not provide good functions for working with them?
glibc is the only recalcitrant left (Solaris, the Linux kernel, Samba and hundreds of other packages already have these functions). Drepper is being absurd and egomaniacal in refusing these functions in.
strlcpy/strlcat make things better
Your argument ignores two simple and completely obvious facts:
First, there are many, many existing usage instances of unsafe string handling functions that can be greatly improved through a trivial conversion to strlcpy/strlcat. It is silly to expect them to all be completely rewritten to use unbounded strings, which can have their own problems that fixed length strings do not (potential memory consumption DoS, integer overflow, etc.)
Second, there are many, many cases where you want or need a fixed length string. Lots of network protocols, file formats and system interfaces require them, so why not provide good functions for working with them?
glibc is the only recalcitrant left (Solaris, the Linux kernel, Samba and hundreds of other packages already have these functions). Drepper is being absurd and egomaniacal in refusing these functions in.