This is the mail archive of the libc-alpha@sourceware.org mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: [PATCH] Implement strlcpy [BZ #178]


David Miller <davem@davemloft.net> writes:

> I think the fact that there are 60 such cases supports my arguments even
> more strongly, because that is how many strlcpy users are even less
> likely to ever change if glibc supports strlcpy too.

I'm pretty sure I have a package for which I'm upstream in Fedora, which
means I represent one of those uses.  (And there's at least INN, for which
I was responsible for introducing strlcpy.)  Based on the previous
conversation, I'll probably eventually end up removing strlcpy entirely in
favor of other techniques, but all my packages that currently use strlcpy
only optionally compile it if it's not in libc.  If it's in libc, the
system version is preferred, since it's presumably more optimized and
possibly safer.

I suspect this is not uncommon among strlcpy users.  (Basically, using
AC_REPLACE_FUNCS.)

-- 
Russ Allbery (eagle@eyrie.org)              <http://www.eyrie.org/~eagle/>


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]