Date: Mon, 30 Oct 2000 18:57:16 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Laszlo Molnar <laszlo DOT molnar AT eth DOT ericsson DOT se>
cc: "Peter J. Farley III" <pjfarley AT banet DOT net>, djgpp-workers AT delorie DOT com
Subject: Re: Bash 2.04 beta 6a
In-Reply-To: <20001030103604.B26090@libra.eth.ericsson.se>
Message-ID: <Pine.SUN.3.91.1001030185539.15587B@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Mon, 30 Oct 2000, Laszlo Molnar wrote:

> Yes, there is a good reason. The private djgpp popen in perl uses a
> delete-on-close flag on the temp file handle - so in case of problems
> it's automatically removed.

Oh yeah, I remember now.

> Some times ago I suggested adding this
> feature to the official libc - but there was no interest.

Actually, IIRC, there was doubt whether automatically removing the file 
in case of failure is a Good Thing: some people look at the contents of 
the temporary file to debug the problem...