Very Computer

Quote:Jung) writes:
>which shells are available for Linux
>I am particular interested in bourne shell compatibles..

Quote:>I just found one drawback of bash on linux:
>The make depend from Smail 3.1.28 was doing nonsense .
>checking the sh scripts I found the problem to set the CASE_NO_NEWLINES

>the bash was not able to work with newlines in arguments inside a case
>switch...

I also detected two other problems with bash 1.12:

 - it wouldn't run the Configure script of trn 3.0 (beta). This will be
   fixed in bash 1.13, but the Configure script has already changed so that
   it works with bash 1.12 too.

 - it does something wrong with passing $* from other shell scripts which are
   included by the `.' command. I detected this when INN 1.4 rejected all
   newgroup messages.

Quote:>ksh blew on some other kind, it just hang at one place or was that
>awfully slower than bash.

        #!/bin/ksh

Zsh gives also problems with Configure scripts.

Quote:>What shells are available for linux and which type they are.
>I know of: bash, ksh, tcsh, zsh.
>I know bas is some how bourne shell compatible
>tcsh somehow csh and ksh also sh..

Arjan

--

Arjan

--

if [ -s foo -a "`cat foo`" = "FOO" ]; then
....

If foo doesn't exist, pdksh still do cat foo since it evaluates
`cat foo` first before everything else.

H.J.

hl> I will make my pdksh 4.8 available in source code when I get time. I
hl> fixed two bugs. There is still one bug hard to fix. That is

hl> if [ -s foo -a "`cat foo`" = "FOO" ]; then
hl> ....

hl> If foo doesn't exist, pdksh still do cat foo since it evaluates
hl> `cat foo` first before everything else.

I wouldn't call this a bug. In fact, I would call the behaviour you
desire a bug. If it doesn't parse the backquotes in the second
argument if the first one is false, how could this ever be compatible
with an external /bin/test ?

Bas.