[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Bug-gnubg] Severe side effects of makebearoff
From: |
Jim Segrave |
Subject: |
Re: [Bug-gnubg] Severe side effects of makebearoff |
Date: |
Thu, 28 Nov 2002 17:02:48 +0100 |
User-agent: |
Mutt/1.4i |
On Thu 28 Nov 2002 (16:41 +0100), Holger wrote:
> At 16:28 28.11.2002 +0100, Jim Segrave wrote:
> >I'm very glad I'm running Unix then.
>
> :-)
>
> However, I'm sure that it's M$ fault. Well, maybe. ;-) It could just be the
> implementation of MinGW.
>
> >Nonetheless, using '&&' should force makebearoff to finish before
> >makebearoff1 can start.
>
> Hmm, no. && also only operates at shell level and only processes the return
> value. Since makebearoff returns without an error, execution is passed on
> to the next command. Am I wrong?
The && should be implemented so that the second command only executes
if the first one is completed successfully. If the first one fails,
the second should never be started.
>
> Btw, there's _no_ output from either makebearoff nor makebearoff1. At other
> times I've seen some.
Yes - makebearoff should output some text about what it's going to do
and a counter to tell you how far it's got (to stderr).
--
Jim Segrave address@hidden