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 v3] Implement strlcpy [BZ #178]


On Sat, 7 Nov 2015, Rich Felker wrote:

> Anyway, in general, if adding a function to glibc is a bad idea,
> adding it in its own separate .so file shipped with glibc is an even
> worse idea. There are no advantages and lots of disadvantages.

While it's trivially true that "adding a function to glibc is a bad idea" 
means it's bad to add it to any library in glibc, existing or new, there 
may well be cases where the conclusion is "it's a good idea to add this 
function to glibc, but in a new library (which might be might not be 
linked in automatically via AS_NEEDED in a .so linker script)".  Cf. 
libmvec or the libinux-syscalls.so.1 discussion.  It's just that I don't 
see strlcpy, strlcat or explicit_bzero as such cases - I see them as cases 
that belong in libc.

-- 
Joseph S. Myers
joseph@codesourcery.com


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