From owner-freebsd-bugs Thu Apr 6 6:50: 6 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id EBA3D37BE25 for ; Thu, 6 Apr 2000 06:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id GAA38889; Thu, 6 Apr 2000 06:50:04 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Thu, 6 Apr 2000 06:50:04 -0700 (PDT) Message-Id: <200004061350.GAA38889@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Sheldon Hearn Subject: Re: bin/16924: tmpfile(3) ignores TMPDIR and always uses /tmp Reply-To: Sheldon Hearn Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/16924; it has been noted by GNATS. From: Sheldon Hearn To: Mike Heffner Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: bin/16924: tmpfile(3) ignores TMPDIR and always uses /tmp Date: Thu, 06 Apr 2000 15:41:20 +0200 On Thu, 06 Apr 2000 09:28:55 -0400, Mike Heffner wrote: > I assume you mean the part of malloc setting ENOMEM. Is there a case > where it wouldn't set ENOMEM? According to the manpage, this is how > malloc(3) should behave. Bleh, please ignore that. I don't know what I've been smoking, but I'm actually the guy who modified the malloc(3) manual page to specifically state that it _does_ set errno! :-) The problem is that the C standard doesn't specify that malloc() sets errno. We should probably mention in malloc(3)'s STANDARDS section that setting errno from malloc() is mandated by the standard and that other implementations can not be relied on to do so. Ciao, Sheldon. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message