Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
To: pjacklam AT online DOT no (Peter J. Acklam)
Cc: "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com>, cygwin AT cygwin DOT com
Subject: Re: /usr/bin/env - Incorrect parsing of #! line?
References: <20020213015400 DOT GI28002 AT redhat DOT com>
	<00a201c1b430$5217b5c0$6600a8c0 AT cherry>
	<20020213015400 DOT GI28002 AT redhat DOT com>
	<4 DOT 3 DOT 1 DOT 2 DOT 20020220155727 DOT 02161d00 AT pop DOT ma DOT ultranet DOT com>
	<4rka371x DOT fsf AT online DOT no>
From: hammond AT csc DOT albany DOT edu (William F. Hammond)
Date: 21 Feb 2002 21:27:01 -0500
In-Reply-To: <4rka371x.fsf@online.no>
Message-ID: <i7d6yyb6a2.fsf@pluto.math.albany.edu>
Lines: 29
User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.1
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

pjacklam AT online DOT no (Peter J. Acklam) writes:

> "Larry Hall (RFK Partners, Inc)" <lhall AT rfk DOT com> wrote:
> 
> > Well if env documentation states a particular behavior and that
> > behavior is not what you see, then there is a bug in env or it's
> > documentation.
> 
> What made me believe that "#!/usr/bin/env perl -w" should work was
> the following part of the documentation for env:

I don't understand why you want to use /usr/bin/env under Cygwin.

Not everything that makes sense under *ix makes sense for Cygwin.

Presumably one runs Cygwin because one does not want to run Linux
so that one can have simultaneous single platform access to Win*
things and Gnu things familiar in *ix contexts.

That said, doesn't it then make sense to use a straight Win* build for
perl so that perl can be used in Win* mode?  Granted that -- and
granted the desire to build environment outside of the Perl script
itself -- one may use either a bat file or an sh script, as
appropriate for the calling context, to create the needed environment.

Either way after building the environment use the syntax:
perl {script-name} {script-arg} ... .

                                    -- Bill

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/