Date: Mon, 30 Oct 2000 10:36:04 +0100 From: Laszlo Molnar To: Eli Zaretskii Cc: "Peter J. Farley III" , djgpp-workers AT delorie DOT com Subject: Re: Bash 2.04 beta 6a Message-ID: <20001030103604.B26090@libra.eth.ericsson.se> References: <4 DOT 3 DOT 1 DOT 0 DOT 20001028153622 DOT 00b18a90 AT pop5 DOT banet DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i In-Reply-To: ; from eliz@is.elta.co.il on Sun, Oct 29, 2000 at 08:17:33AM +0200 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 Sun, Oct 29, 2000 at 08:17:33AM +0200, Eli Zaretskii wrote: > On Sat, 28 Oct 2000, Peter J. Farley III wrote: > > At 09:25 AM 10/28/00 +0200, Eli Zaretskii wrote: > > > > >Note that popen/pclose from our libc also redirect handles with > > >dup/dup2 and call system() to run the subsidiary program. > > I guess Laszlo put those in before the current popen/pclose were > > available. > I doubt that: our popen/pclose is mostly unchanged from what was released > with v2.0. > > Better, I think, if we try to use what's in libc, so that > > future changes aren't lost to perl. I'll try removing his > > perl-specific versions and make sure everything still works. > I'd suggest to as Laszlo first, in cased there's a good reason for what > he did. 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. Some times ago I suggested adding this feature to the official libc - but there was no interest. So I've done it privately because it looked useful. Laszlo