From: Malcolm Kay <malcolm.kay@internode.on.net>
To: Eric Blake <eblake@redhat.com>
Cc: dash@vger.kernel.org
Subject: Re: if then elif then else fi -- Problem report
Date: Tue, 29 Jun 2010 10:38:31 +0930 [thread overview]
Message-ID: <201006291038.31206.malcolm.kay@internode.on.net> (raw)
In-Reply-To: <4C28A1FA.1090306@redhat.com>
Eric,
Thanks for the clarification.
I had assumed that 'dash' aimed to be a faster replacement for
the classical Bourne shell 'sh' as implemented in BSD systems,
and this seemed to be confirmed when all the man pages I've been
able to find were more or less direct copies of BSD 'sh' pages.
As it is I feel the man pages should not only be fixed in this
respect, but also such differences to classical 'sh'
implementations should be high lighted.
On Mon, 28 Jun 2010 10:52 pm, Eric Blake wrote:
> . . .
>
> Therefore, the bug is in the man page. Per POSIX,
> http://www.opengroup.org/onlinepubs/9699919799/utilities/V3_ch
>ap02.html#tag_18_09_03 "A list is a sequence of one or more
> AND-OR lists separated by the operators ';' and '&' and
> optionally terminated by ';' , '&' , or <newline>."
While I agree with your conclusions, I would note that POSIX
defines "if ... else etc." in terms of 'compound_list' rather
than 'list' so the above definition of 'list' is not really
relevant. By my reading of your reference it seems POSIX defines
'list' and 'compound_list' independently but fails to clarify
the difference if any.
Malcolm
next prev parent reply other threads:[~2010-06-29 1:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 12:56 if then elif then else fi -- Problem report Malcolm Kay
2010-06-28 13:22 ` Eric Blake
2010-06-29 1:08 ` Malcolm Kay [this message]
2010-06-29 12:56 ` Eric Blake
2010-07-04 21:50 ` Sven Mascheck
2010-07-06 7:48 ` Malcolm Kay
2010-07-06 20:49 ` Sven Mascheck
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=201006291038.31206.malcolm.kay@internode.on.net \
--to=malcolm.kay@internode.on.net \
--cc=dash@vger.kernel.org \
--cc=eblake@redhat.com \
/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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.