From owner-freebsd-hackers  Sat Feb 24 12:43:55 2001
Delivered-To: freebsd-hackers@freebsd.org
Received: from guild.plethora.net (guild.plethora.net [205.166.146.8])
	by hub.freebsd.org (Postfix) with ESMTP id 902DA37B67D
	for <freebsd-hackers@freebsd.org>; Sat, 24 Feb 2001 12:43:48 -0800 (PST)
	(envelope-from seebs@guild.plethora.net)
Received: from guild.plethora.net (seebs@localhost.plethora.net [127.0.0.1])
	by guild.plethora.net (8.10.1/8.10.1) with ESMTP id f1OKhl618691
	for <freebsd-hackers@freebsd.org>; Sat, 24 Feb 2001 14:43:47 -0600 (CST)
Message-Id: <200102242043.f1OKhl618691@guild.plethora.net>
From: seebs@plethora.net (Peter Seebach)
Reply-To: seebs@plethora.net (Peter Seebach)
To: freebsd-hackers@freebsd.org
Subject: Re: Setting memory allocators for library functions. 
In-reply-to: Your message of "Sat, 24 Feb 2001 21:42:28 +0100."
             <9402.983047348@critter> 
Date: Sat, 24 Feb 2001 14:43:47 -0600
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

In message <9402.983047348@critter>, Poul-Henning Kamp writes:
>>Well, no, but the sole available definition of "portable" says that it is
>>"portable" to assume that all the memory malloc can return is really
>>available.

>No, this is not a guarantee.

Yes, it is.  If the memory isn't available, malloc returns NULL.

>We also don't guarantee that you can read a file just because you
>managed to open it (disk errors, nfs servers going away, forced
>unmounts).

Sure.  And all the IO functions have return codes.

-s

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message