Date:	Fri, 10 Jan 2003 21:58:26 +0300
From:	"Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il>
Sender:	halo1 AT zahav DOT net DOT il
To:	djgpp-workers AT delorie DOT com
Message-Id:	<2110-Fri10Jan2003215826+0200-eliz@is.elta.co.il>
X-Mailer:	emacs 21.3.50 (via feedmail 8 I) and Blat ver 1.8.9
In-reply-to:	<1042022855.32477.13.camel@leeloo> (message from Tim Van Holder
	on 08 Jan 2003 11:47:36 +0100)
Subject:	Re: m4 port: return program name as 'm4' not '/some/path/m4.exe'
	[PATCH]
References:	<E18VAre-0000gx-00 AT phekda DOT freeserve DOT co DOT uk>
	<003801c2b559$f33a0d60$0100a8c0 AT acp42g>
	<3E19BEAE DOT 7CC5B46C AT phekda DOT freeserve DOT co DOT uk>
	<200301061840 DOT h06IebI26175 AT envy DOT delorie DOT com>
	<3E1B35F9 DOT DC4EA825 AT phekda DOT freeserve DOT co DOT uk>
	<1042022855 DOT 32477 DOT 13 DOT camel AT leeloo>
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

> From: Tim Van Holder <tim DOT van DOT holder AT pandora DOT be>
> Date: 08 Jan 2003 11:47:36 +0100
> 
> Not sure what our bash does now; if it uses exec*(), it can pass image
> name and argv0 separately to provide exact Unix-like behaviour.  Maybe
> system() could be changed accordingly as well, leaving only invocations
> from command.com to get the 'full' path as argv0.

I believe you meant `spawn*', not `exec*'.

Since our `system' already uses `spawn*' where possible, fixing
`spawn*' will fix `system' automatically.

If `system' doesn't call `spawn*', it means the subprogram is invoked
via the shell, in which case we don't have any control on argv[0].

- Raw text -