Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 6 Jun 2000 09:40:02 -0700 (PDT)
From:      mi@privatelabs.com
To:        freebsd-ports@FreeBSD.org
Subject:   Re: ports/19047: net/arpwatch patched to use tmpfile() instead of   mktemp()
Message-ID:  <200006061640.JAA18782@freefall.freebsd.org>

next in thread | raw e-mail | index | archive | help
The following reply was made to PR ports/19047; it has been noted by GNATS.

From: mi@privatelabs.com
To: Maxim Sobolev <sobomax@FreeBSD.org>
Cc: FreeBSD-gnats-submit@FreeBSD.org, arpwatch@ee.lbl.gov
Subject: Re: ports/19047: net/arpwatch patched to use tmpfile() instead of  
 mktemp()
Date: Tue, 6 Jun 2000 12:34:37 -0400 (EDT)

 On  6 Jun, Maxim Sobolev wrote:
 = Mikhail Teterin wrote:
 = 
 = > >Synopsis: net/arpwatch patched to use tmpfile() instead of mktemp()
 = 
 = Why not mkstemp()? According to  the tmpfile() man page, this function
 = may not  be portable across  platforms. So, probably, you  have better
 = chances that your patches will be  accepted by the authors of arpwatch
 = if you will use mkstemp() instead.
 
 Because I need FILE  * instead of a file descriptor  and because I think
 the name tmpfile is easier to understand then mkstemp. Also tmpfile will
 obey  TMPDIR environment  variable and  it does  not need  the character
 template.  I think,  tmpfile  is a  better  choice, although  tmpfile(3)
 disagrees.
 
 All of this is hardly a big  problem, but I believe the file looks nicer
 and easier to read this way.
 
 As far as the standards go, from tmpfile(3):
 
 STANDARDS
      The tmpfile() and tmpnam() functions conform to ISO 9899: 1990
      (``ISO C'').
 
 So compatability should not be a problem... Yours,
 
 	-mi
 
 


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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006061640.JAA18782>