Date: 22 Oct 1998 10:40:10 +0200 From: dag-erli@ifi.uio.no (Dag-Erling C. =?iso-8859-1?Q?Sm=F8rgrav?= ) To: Matthew Dillon <dillon@apollo.backplane.com> Cc: Peter Wemm <peter@netplex.com.au>, Bruce Evans <bde@zeta.org.au>, cvs-all@FreeBSD.ORG, cvs-committers@FreeBSD.ORG Subject: Re: cvs commit: src/lib/libc/stdio mktemp.c Message-ID: <xzphfwxt2fp.fsf@hrotti.ifi.uio.no> In-Reply-To: Matthew Dillon's message of "Wed, 21 Oct 1998 09:08:56 -0700 (PDT)" References: <199810210245.KAA14596@spinner.netplex.com.au> <199810210437.VAA01979@apollo.backplane.com> <xzpvhleqo8u.fsf@grjottunagard.ifi.uio.no> <199810211608.JAA06244@apollo.backplane.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew Dillon <dillon@apollo.backplane.com> writes: > :Matthew Dillon <dillon@apollo.backplane.com> writes: > :> I could go either way. My personal preference would be to fix the manual > :> page to read 'mode 0600 masked by the current umask' and *not* put in the > :> fchmod(), because I can certainly see a program expecting to create a > :> file with read-only permissions by setting the umask and calling > :> mkstemp() to get the read+write descriptor. It would be phenominally dumb > :> programmer to depend on it, but I can see it. > :So we should adapt FreeBSD to be nice to phenomenally dumb > :programmers? I feel a rerun of the fclose(NULL) debate coming... > Huh? That's kind of an out-of-the-blue comment. I have no idea what > you are talking about. I was referring to the argument about whether or not fclose() should dump core when passed a NULL pointer. DES -- Dag-Erling Smørgrav - dag-erli@ifi.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?xzphfwxt2fp.fsf>