`Hiding' libc symbols

[Andrey A. Chernov]

On Tue, May 06, 2003 at 21:39:51 +0200, Dag-Erling Smorgrav wrote:

> No.  It will lead to surprising results if the file that includes
> <math.h> really does use sin(), but if it doesn't there is no reason
> why the other file can not define an external symbol named sin because
> sin is in the application namespace in that file.

If some file includes <math.h> even not using any functions from it, it 
declares namespace visibility for whole application.

> > About c), at this moment we discuss functions namespace only, i.e. linker 
> > "T" class.
> 
> So you admit that your solution is incomplete?  In that case, why do
> you insist that it is superior to Jacques Vidrine's solution, which
> addresses all cases without requiring us take the linker off the
> vendor branch and make it unusable for non-hosted applications?

It is incomplete in the same way as Jacques one since we both discuss only
functions so far. The difference is that my approach move us towards
standards conformance while Jacques one to opposite direction.