Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<19990618013506.A22404@ba.best.com>
Date:	Fri, 18 Jun 1999 01:35:06 -0400
From:	Glenn Spell <glenn AT gs DOT fay DOT nc DOT us>
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	Re: "sed" bug?
Mail-Followup-To:	cygwin AT sourceware DOT cygnus DOT com
References:	<19990617123626 DOT 6913 DOT rocketmail AT web113 DOT yahoomail DOT com> <m10ufIo-007vP6C AT light DOT lbin DOT com>
Mime-Version:	1.0
X-Mailer:	Mutt 0.93.2i
In-Reply-To:	<m10ufIo-007vP6C@light.lbin.com>; from "itz@lbin.com" on Thu, Jun 17, 1999 at 09:46AM
Organization:	the aerie

On 17 Jun 1999 at 9:46AM (-0700) itz AT lbin DOT com wrote:

> Is ash supposed to be a full implementation os the POSIX shell?

Not yet. On some platforms ash is in the process of being changed to
conform with the POSIX.2 specification.

> If not, you'll always run into scripts that are hash-banged with
> #!/bin/sh but contain constructs ash won't understand.

I've read that many Linux packages provide scripts hash-banged with
"#!/bin/sh" that depend on "bashisms"... as if bash was some sort of
standard.  That would present problems not only for ash but for any
POSIX shell as well.

-glenn

-- 
 )      Glenn Spell <glenn AT gs DOT fay DOT nc DOT us>      )   _       _____
 )   Fayetteville, North Carolina, U. S. A.   )_ (__\____o /_/_ |
 )  _  _  _  _  _  _  _  _  _  _  _  _  _  _  )   >-----._/_/__]>
 )- blue skies - happy trails - sweet dreams -)             `0  |

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -