From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Zoltan Hidvegi <hzoli@cs.elte.hu>,
borsenkow.msk@sni.de, zsh-workers@math.gatech.edu
Subject: Re: sh compatibility again :->
Date: Sun, 11 Aug 1996 21:36:34 -0700 [thread overview]
Message-ID: <960811213634.ZM4881@candle.brasslantern.com> (raw)
In-Reply-To: Zoltan Hidvegi <hzoli@cs.elte.hu> "Re: sh compatibility again :->" (Aug 12, 4:18am)
On Aug 12, 4:18am, Zoltan Hidvegi wrote:
} Subject: Re: sh compatibility again :->
}
} Andrej Borsenkow wrote:
} [...]
} > 1. It doesn't like malformed constructs like
} >
} > A="`cat /some/file" (note missed backtick)
} >
} > zsh tries to parse command substitution behind closing double-quote, and
} > ends up with `missing "' at the end of script. Our /bin/sh stops at
} > closing double-quote. In POSIX the result is undefined - thus, techically
} > neither violate it.
}
} I copied the behaviour of bash here. pdksh also behaves this way.
Right; if I recall correctly, bash and ksh both permit stuff like:
$ echo "foo `echo "bar baz"` boing"
That is, bash and ksh nest double quotes inside backticks. Old-fashioned
Bourne shell, on the other hand, does NOT permit nesting of double quotes,
even inside backticks. So in bash/ksh the above is parsed as
(echo) (foo `echo "bar baz"` boing)
but in sh it is
(echo) (foo `echo bar) (baz` boing)
The only way to resolve this would be with yet another option, SH_QUOTES
or some such. Worth it? Dunno.
} > But the following things could probably be fixed
} >
} > 4. Traditional /bin/sh interprets `set -' as set +xv.
}
} OK. I've changed that. set - will be the same as set +xv and
} set - args will be the same as set +xv -- args.
Hmm. So what's the approved way of setting $1 to "-x"? `set -- -x`?
And is `set --` equivalent to `shift $#`, since `set -` is not?
Are you sure `set - args` should act like `set +xv -- args`?
I can't say I'm entirely excited about this change.
} > 5. Currently zsh sets BSD_ECHO when running as sh. Our sh does support
} > escapes in echo; I recall that SCO sh does it as well. I don't know about
} > others. What about relaxing it? If scripts doesn't rely upon escapes in
} > echo, it would make no harm.
}
} I'll try to write a configure check for the echo style of /bin/sh and use
} that.
Eww, no. Let's pick one behavior and stick with it, please. The default
options, even in an emulation mode, shouldn't vary from one installation
to the next! It's been a long time since I encountered an sh that didn't
have a builtin SysV-style echo -- BSD_ECHO is needed mostly for csh
compatibility. I'd vote for leaving BSD_ECHO off when run as "sh".
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.nbn.com/people/lantern
New male in /home/schaefer:
>N 2 Justin William Schaefer Sat May 11 03:43 53/4040 "Happy Birthday"
next prev parent reply other threads:[~1996-08-12 4:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-31 21:11 Announcement draft Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01 6:36 ` Bas V. de Bakker
1996-08-01 8:31 ` Peter Stephenson
1996-08-01 9:04 ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01 9:10 ` Announcement draft Andrej Borsenkow
1996-08-01 13:49 ` Here docs Peter Stephenson
1996-08-01 14:07 ` Zoltan Hidvegi
1996-08-01 16:27 ` More Configure problems Peter Stephenson
1996-08-01 17:40 ` Peter Stephenson
1996-08-01 17:55 ` Zoltan Hidvegi
1996-08-01 21:03 ` Zoltan Hidvegi
1996-08-01 23:30 ` Zoltan Hidvegi
1996-08-02 8:32 ` Peter Stephenson
1996-08-02 10:03 ` Andrej Borsenkow
1996-08-02 13:29 ` Zoltan Hidvegi
1996-08-02 1:03 ` Zefram
1996-08-01 14:42 ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12 2:18 ` Zoltan Hidvegi
1996-08-12 4:36 ` Bart Schaefer [this message]
1996-08-12 5:00 ` Zefram
1996-08-12 6:01 ` Bart Schaefer
1996-08-12 6:34 ` Bart Schaefer
1996-08-12 6:20 ` Andrej Borsenkow
1996-08-12 15:29 whukriede
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=960811213634.ZM4881@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=borsenkow.msk@sni.de \
--cc=hzoli@cs.elte.hu \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).