This is the mail archive of the
mailing list for the Cygwin project.
RE: /usr/bin/env - Incorrect parsing of #! line?
- From: Chet Ramey <chet at nike dot ins dot cwru dot edu>
- To: gsw at agere dot com
- Cc: cygwin at cygwin dot com, dgluss at marple-tech dot com, pjacklam at online dot no, chet at po dot cwru dot edu
- Date: Wed, 13 Feb 2002 09:47:37 -0500
- Subject: RE: /usr/bin/env - Incorrect parsing of #! line?
- Read-receipt-to: chet@po.CWRU.Edu
- Reply-to: chet at po dot CWRU dot Edu
> I think DG's and PJA's original assessment was correct and
> BASH should be modified. Support for cross-platform scripts
> is important, and the #!/bin/env trick is used frequently.
How is changing bash going to do anything? The kernel takes
care of executing files with a `#!' magic number. I presume
that the cygwin dll handles this.
There is an incompatibility between the linux kernel and other
Unices in the way they parse arguments after the interpreter
name, but that's not really bash's business.
``The lyf so short, the craft so long to lerne.'' - Chaucer
( ``Discere est Dolere'' -- chet)
Chet Ramey, CWRU chet@po.CWRU.Edu http://cnswww.cns.cwru.edu/~chet/
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Bug reporting: http://cygwin.com/bugs.html