Message-Id: <4.3.1.0.20001027192402.00b199b0@pop5.banet.net> X-Sender: usbanet DOT farley3 AT pop5 DOT banet DOT net X-Mailer: QUALCOMM Windows Eudora Version 4.3.1 Date: Fri, 27 Oct 2000 19:33:02 -0400 To: djgpp-workers AT delorie DOT com From: "Peter J. Farley III" Subject: Re: Bash 2.04 beta 6a In-Reply-To: <7458-Fri27Oct2000114600+0200-eliz@is.elta.co.il> References: <200010270805 DOT KAA00023 AT lws256 DOT lu DOT erisoft DOT se> <200010270805 DOT KAA00023 AT lws256 DOT lu DOT erisoft DOT se> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed 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 At 11:46 AM 10/27/00 +0200, you wrote: >I'm not sure this is the correct way of testing this. The original >command invoked ECHO differently ("echo #foo|"), which might be >invoking the shell in some subtly different way, e.g. because it >redirects the standard handles. I think you need to test the >interactive/non-interactive aspect in the same way. I will isolate the failing perl test code and test it separately on both DJGPP and Linux and see if I can generate more info. As you said in an earlier note, we need to know how it is that perl does this in *ix environments to see what path we need to take. BTW, the DJGPP perl "popen"/"pclose" wrapper/substitutes that Laszlo pointed me to use system() exclusively for the command execution, both for read and write pipes. But the wrapper also uses dup/dup2 on stdout (for read pipes) or stdin (for write pipes) around the calls to system(). So DJGPP perl is using strictly system(), and now I need to find out what perl uses elsewhere. And maybe what a *ix popen/pclose really use. More as I discover it. --------------------------------------------------------- Peter J. Farley III (pjfarley AT dorsai DOT org OR pjfarley AT banet DOT net)