X-Authentication-Warning: delorie.com: mailnull set sender to djgpp-workers-bounces using -f Date: Mon, 17 Dec 2001 15:47:39 +0200 (WET) From: Andris Pavenis X-Sender: pavenis AT ieva06 To: Eli Zaretskii Cc: Tim Van Holder , djgpp-workers AT delorie DOT com Subject: Re: Weird system() thing (was Re: The Bash 2.05 fixinc.sh bug) In-Reply-To: Message-ID: 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, 17 Dec 2001, Eli Zaretskii wrote: > > > after > > > that shell is exited, the following does not: > > > > > > int > > > main(void) > > > { > > > system(""); > > > system("Foo=bar"); > > > } > > > > I guess Your executable were named foo.exe. > > ======== > > That could indeed explain the problem, but then why didn't the > previous example, the one with a single system("Foo=bar"), cause the > same infinite series of subprogram invocations? > Maybe the first one were called differently > > As far as I tested system ("Foo=bar") is interpretted as > > 'Foo "=bar"' > > This interpretation is in COMMAND.COM, not in `system': an unquoted > `=' characters is treated as a delimiter by COMMAND.COM. (Old > versions of COMMAND.COM, such as the one in DOS 5.0, don't support > quoting, so `=' is _always_ a delimiter there.) > > (COMMAND.COM is in this example invoked by `system' because it doesn't > find a program called `Foo=bar', with or without an executable > extension.) > > >