On Wed, 12 Jun 2013 21:18:05 +0200 Stefan Fritsch <[email protected]> wrote:
> It is a useful function. Disallowing it breaks ISO-C compliant code > for no good reason. There has been a complaint by a module author. > Allowing it does not use any memory because the function is already > in libc. Working around the missing function requires additional > code, which uses memory and may contain bugs. What more reasons do > you need? I'm +1... we should only perform such abuses of stdc / clib within the scope of our own -private- headers. Modifying these in our headers meant for public consumption is a very irritating thing to do. If this were hidden in some CORE_PRIVATE scope then I would have been fine with leaving things as is.
