Date: Sat, 8 Feb 2003 18:07:17 -0500
Message-Id: <200302082307.h18N7HD26685@envy.delorie.com>
X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT delorie DOT com using -f
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
CC: abc AT anchorageinternet DOT org
In-reply-to: <200302082147.h18Lljri034387@en26.groggy.anc.acsalaska.net>
	(abc AT anchorageinternet DOT org)
Subject: Re: #! bash bug
References:  <200302082147 DOT h18Lljri034387 AT en26 DOT groggy DOT anc DOT acsalaska DOT net>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> this does seem to be an ambiguous area,

No, it's not.  The standard tells us how to act, we act that way.

> interpreter on the shebang line, passing everything after
> "#!/interpreter [arg]" to an "eval" or "sh -c" ...

The problem is, we're not talking about what happens in bash.  We're
talking about a function call that's built into *every* djgpp program
that needs it.  When a djgpp program execs a script, bash is not
involved at all.

If you want to see the source for the function that actually handles
this, it's script_exec() in src/libc/dos/process/dosexec.c:

http://www.delorie.com/bin/cvsweb.cgi/djgpp/src/libc/dos/process/dosexec.c