From dev-return-8614-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Fri Dec 06 11:30:53 2002 Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 22570 invoked by uid 500); 6 Dec 2002 11:30:52 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 22558 invoked from network); 6 Dec 2002 11:30:51 -0000 Date: Fri, 6 Dec 2002 12:30:47 +0100 (CET) From: Dirk-Willem van Gulik To: dev@apr.apache.org Subject: Re: APR_TMP_DIRECTORY In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Going back in the discussion; and looking at the code - what do we *need* it for ? Is it just to construct effective replacements for the tmpfile/tempnam /tmpnam trio ? Or is there also a valid direct use of the name of that directory ? As I certainly would like to not encourage the use of pseudo name space management along the lines of snprintf(..'%s/myapp.%d',tmpdir,getpid()) when an OS contract offers you better. Dw -- Dirk-Willem van Gulik