`Hiding' libc symbols

[Ben Mesander]

Daniel Eischen writes:
 > On Tue, 6 May 2003, Andrey A. Chernov wrote:
 > > On Mon, May 05, 2003 at 18:14:45 -0400, Daniel Eischen wrote:
 > > Especially when I don't understands threads details. At this stage we just
 > > discuss here how to make things better. My point will be clear answering
 > > on this simple question:
 > > 
 > > What produce less errors in application and libraries?
 > > a) Allow application to replace any standard function.
 > 
 > I thought Jacques found lots of ports that replaced standard
 > functions...

In addition to ports which override libc functions like printf() for
ease of porting, there are important ports, such as the Boehm garbage
collector for C/C++ or electric fence, which _depend_ upon the ability
to override libc functions such as malloc() and free().

Whatever decision is eventually made must allow such ports to
function.

This has been brought up once before, but I do not see how any of the
advocates for change have addressed it.

--Ben