From 4803873159205322295
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 1149ec,f5b50f79e3b33c8d
X-Google-Attributes: gid1149ec,public
X-Google-Thread: f78e5,c0143c56db298752
X-Google-Attributes: gidf78e5,public
X-Google-ArrivalTime: 1994-09-18 04:02:46 PST
Path: bga.com!news.sprintlink.net!howland.reston.ans.net!spool.mu.edu!bloom-beacon.mit.edu!ai-lab!life.ai.mit.edu!tmb
From: tmb@arolla.idiap.ch (Thomas M. Breuel)
Newsgroups: comp.std.c,comp.std.c++
Subject: Re: malloc calls FROM the standard library (was: Re: Question on 5.2.3.)
Date: 16 Sep 1994 23:10:04 GMT
Organization: IDIAP (Institut Dalle Molle d'Intelligence Artificielle
	Perceptive)
Lines: 17
Message-ID: <TMB.94Sep17011004@arolla.idiap.ch>
References: <CvvDzK.2E8@cogsci.ed.ac.uk> <1994Sep10.033223.23015@nlm.nih.gov>
	<352ps8$j32@reuter.cse.ogi.edu> <354jbs$54q@ritz.cec.wustl.edu>
	<Cw3yn9.Inx@scone.london.sco.com>
Reply-To: tmb@idiap.ch
NNTP-Posting-Host: arolla.idiap.ch
In-reply-to: clive@sco.com's message of Wed, 14 Sep 1994 07:11:31 GMT
Xref: bga.com comp.std.c:2985 comp.std.c++:4342

In article <Cw3yn9.Inx@scone.london.sco.com> clive@sco.com (Clive D.W. Feather) writes:
|However, the Standard cannot rely on this, hence its wording.
|
|Another case is that of monolithic shared libraries. Some implementations
|of shared libraries link the whole library into one block, resolving all
|internal references. So if a library function refers to "malloc", it will
|get the one in the library, no matter whether or not there is a user
|function called "malloc". This arrangement also conforms to the Standard.

The C standard permits an implementation to do lots of things.
However, that doesn't mean that doing such things is a good idea.

Resolving malloc calls within the standard library is generally a bad
idea, since most user-supplied replacements of malloc will not work in
the presence of the original, system-supplied version of malloc.

				Thomas.