On Fri, 6 Jan 2023, Alejandro Colomar via Libc-alpha wrote: > P.S.: To compensate for the time I'm taking from you, I'm preparing a patch > to remove rawmemchr(3) from glibc. I'll send it when it's "ready". Although Don't waste your time. The criterion for removing a function is something close to "never did anything meaningful or useful; no binary could ever have successfully used the function with the ABI with which it was defined"; otherwise we'd need a compelling case for how removing the function can't break any existing binaries or sources we'd care about. Even turning a function into a compat symbol, so making it unavailable to new programs (while keeping it for existing binaries and keeping glibc tests of that compat symbol), requires a much stronger deprecation basis than "there are standard functions that are just as good". And marking functions as deprecated with an attribute in headers - normally desirable several releases before making a function into a compat symbol, at least - also needs such a stronger deprecation basis; nothing in this thread suggests any basis for marking *any* string functions as deprecated to me. -- Joseph S. Myers joseph@xxxxxxxxxxxxxxxx
