Re: [PATCH] latest ash has broken 'echo' command
On Fri, Oct 22, 1999 at 04:02:43PM +0200, Marek Habersack wrote:
> * Herbert Xu said:
>
> > Allowed is not the same as mandated. When you write scripts that are POSIX
> > compliant, you have to take into account *all* POSIX shells, not just the on
> > you've got. Otherwise you're writting shell scripts just for your own shell.
> True, but I have to KNOW wheter the feature is supported by the given
> product or not, right? How else can I adapt to different implementations? A
You're not supposed to adapt to ash! You're supposed to be writing shells
which only uses features required by POSIX.2.
> standard that forbids (in effect) using its optional elements by not
> providing means to detect whether these are supported or not is broken and
> should be changed in that respect. How about:
If you use features that are not required by a standard, you are in effect
restricting the the set of shells that can execute your script to those
that implement the features.
--
Debian GNU/Linux 2.1 is out! ( http://www.debian.org/ )
Email: Herbert Xu ~{PmV>HI~} <herbert@gondor.apana.org.au>
Home Page: http://gondor.apana.org.au/~herbert/
PGP Key: http://gondor.apana.org.au/~herbert/pubkey.txt
Reply to: