zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-workers@sunsite.dk (Zsh hackers list)
Subject: Re: PATCH Re: [doogie@brainfood.com: Bug#163237: zsh barfs on valid shell]
Date: Mon, 07 Oct 2002 11:59:09 +0100	[thread overview]
Message-ID: <7302.1033988349@csr.com> (raw)
In-Reply-To: ""Bart Schaefer""'s message of "Fri, 04 Oct 2002 03:57:21 -0000." <1021004035721.ZM2643@candle.brasslantern.com>

"Bart Schaefer" wrote:
> On Oct 3,  4:43pm, Clint Adams wrote:
> } Subject: [doogie@brainfood.com: Bug#163237: zsh barfs on valid shell]
> }
> } This happens under emulate -R sh as well.
> } 
> } ----- Forwarded message from Adam Heath <doogie@brainfood.com> -----
> } 
> } case foo in (foo)echo foo;;(bar)echo bar;;esac
> } zsh:zsh: parse error near `foo'
> 
> This is because "(foo)echo" is being parsed as a file pattern [equivalent
> to "(foo|foo)echo" for those who don't immediately see why it's being
> parsed that way].
> 
> This is an inherent ambiguity in using parens for pattern grouping and is
> going to have to stay the way it is when not in emulation mode.

An option `case_balance_parens' would be a possibility.  The reasoning
for this would be (1) balancing the parentheses is neater anyway, so
having a test to force better syntax is useful (2) inside $(...),
balancing is essential, so using the option makes it consistent.  It
couldn't be on by default, though, so you wouldn't get it with `emulate
zsh', which makes it less useful.

The SH_GLOB test is definitely better for Bourne-style use.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK                          Tel: +44 (0)1223 692070


**********************************************************************
The information transmitted is intended only for the person or
entity to which it is addressed and may contain confidential 
and/or privileged material. 
Any review, retransmission, dissemination or other use of, or
taking of any action in reliance upon, this information by 
persons or entities other than the intended recipient is 
prohibited.  
If you received this in error, please contact the sender and 
delete the material from any computer.
**********************************************************************


      reply	other threads:[~2002-10-07 10:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-03 20:43 Clint Adams
2002-10-04  3:57 ` PATCH " Bart Schaefer
2002-10-07 10:59   ` Peter Stephenson [this message]

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=7302.1033988349@csr.com \
    --to=pws@csr.com \
    --cc=zsh-workers@sunsite.dk \
    /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).