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
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
X-WM-Posted-At:	avacado.atomice.net; Thu, 24 Oct 02 02:11:39 +0100
From:	"Chris January" <chris AT atomice DOT net>
To:	"Cygwin AT Cygwin DOT Com" <cygwin AT cygwin DOT com>
Subject:	RE: "==" operand not found
Date:	Thu, 24 Oct 2002 02:11:39 +0100
Message-ID:	<LPEHIHGCJOAIPFLADJAHOEJHCPAA.chris@atomice.net>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
In-Reply-To:	<5.1.0.14.2.20021023172357.01fdfaf0@pop3.cris.com>
Importance:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

> Unix and POSIX programming environments don't promise the kind of
> "write-once-run-anywhere" property that Java does (or did). Look
> around and
> you'll see lots of scripts that use "uname" to condition details of their
> operation, when necessary. In the case of "features" like non-standard
> operator synonyms, I think it's best simply to avoid them. Personally, I
> have a pretty fast system, and I often just use "/bin/bash" explicitly in
> the #! lines, but even that is risky, since that executable isn't
> guaranteed to exist (the whole #! thing, lacking PATH searching, is a
> portability problem).

perhaps a little offtopic, but you can use /usr/bin/env <program name> to
search for a program using the current path, e.g.:
#!/usr/bin/env perl
means you don't need to know where perl is installed.

Chris


--
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/

- Raw text -