From owner-freebsd-hackers  Sun May 14 12:10:25 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: from orthanc.ab.ca (orthanc.ab.ca [207.167.3.130])
	by hub.freebsd.org (Postfix) with ESMTP id 5DB1137BE51
	for <freebsd-hackers@FreeBSD.ORG>; Sun, 14 May 2000 12:10:14 -0700 (PDT)
	(envelope-from lyndon@orthanc.ab.ca)
Received: from orthanc.ab.ca (localhost [127.0.0.1])
	by orthanc.ab.ca (8.10.0.Beta11/8.10.0.Beta6) with ESMTP id e4EJ9iN09199;
	Sun, 14 May 2000 13:09:45 -0600 (MDT)
Message-Id: <200005141909.e4EJ9iN09199@orthanc.ab.ca>
To: James Howard <howardjp@wam.umd.edu>
Cc: freebsd-hackers@FreeBSD.ORG
Subject: Re: mktemp() vs. mkstemp() 
In-reply-to: Your message of "Sun, 14 May 2000 14:49:28 EDT."
             <200005141849.OAA21071@rac10.wam.umd.edu> 
Date: Sun, 14 May 2000 13:09:44 -0600
From: Lyndon Nerenberg <lyndon@orthanc.ab.ca>
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>>>>> "James" == James Howard <howardjp@wam.umd.edu> writes:

    James> mkstemp() returns an integer file descriptor whereas normal
    James> people use FILE * pointers, including the author of this
    James> port.  How about an mkftemp() which wraps around mkstemp()
    James> and does an fdopen()?

Is it that much work to add

   if ((stream=fdopen(fd, mode)) == NULL)
      err(...);

after a mkstemp call? If you use it that much you can define a function
in your application. There's no need to add a non-portable routine
to libc for this.

--lyndon


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