Re: another baby step - namespace adjustments

[DJ Delorie <dj at redhat dot com>]

> It's not that it's not portable enough, it's that jumping through the
> necessary hoops to link cc1 against libm.so when and only when this is
> required is too much trouble.
> 
> It is inappropriate to call this routine sqrt() unless it meets the
> accuracy requirements of the C standard, which requires considerable
> additional complexity.  That is why it has a nonstandard name.

I fully understand the reasons why you're using that function.  But
I'm looking at it from libiberty's point of view.  This function
doesn't meet the criteria most libiberty functions do:

1. Provide a standard function that is missing on some platforms.
2. Provide a standard function that is broken on some platforms.
3. Provide a function that is widely used by many gnu projects.
4. Provide a common function that is difficult to implement portably.

Given that there is a standard function that nearly all platforms
provide in a standard library, I find it difficult to justify adding a
non-standard semi-compatible replacement to libiberty for it.