All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Nieder <jrnieder@gmail.com>
To: Chet Ramey <chet.ramey@case.edu>
Cc: Stefano Lattarini <stefano.lattarini@gmail.com>, dash@vger.kernel.org
Subject: Re: [BUG] dash doesn't report syntax error when it should on stray "fi"
Date: Mon, 23 Apr 2012 14:54:58 -0500	[thread overview]
Message-ID: <20120423195458.GB13576@burratino> (raw)
In-Reply-To: <4F95B1F8.8080502@case.edu>

Chet Ramey wrote:

> The way I read 2.10.2, Posix requires that the "fi" resolve to the
> reserved word `fi' in this case, since it's in a position where a
> command name is expected (Rule 1, [Command Name]).  I would think that
> would make it a syntax error in any application, conforming or not.

Yes, I think you're right.

For some reason I thought that using reserved words in ways not
permitted by the grammar produced undefined behavior, to support
shells with extensions like the arithmetic "for".  But now that I read
more closely, it looks like "function", "[[", "]]", and "select"
produce unspecified behavior but everything else is pretty well
specified.  Thanks for clarifying.

  reply	other threads:[~2012-04-23 19:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 16:53 [BUG] dash doesn't report syntax error when it should on stray "fi" Stefano Lattarini
2012-04-23 17:03 ` Jonathan Nieder
2012-04-23 17:09   ` Stefano Lattarini
2012-04-23 19:27   ` Chet Ramey
2012-04-23 19:44     ` Jonathan Nieder
2012-04-23 19:48       ` Chet Ramey
2012-04-23 19:54         ` Jonathan Nieder [this message]
2012-04-24 22:47           ` Jilles Tjoelker
2012-04-23 19:53       ` Stefano Lattarini

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=20120423195458.GB13576@burratino \
    --to=jrnieder@gmail.com \
    --cc=chet.ramey@case.edu \
    --cc=dash@vger.kernel.org \
    --cc=stefano.lattarini@gmail.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.