From: Peter Stephenson <pws@cambridgesiliconradio.com>
To: zsh-workers@sunsite.auc.dk (Zsh hackers list)
Subject: Re: Bug in ${(z)...} lexing, or what?
Date: Wed, 12 Jul 2000 11:40:00 +0100 [thread overview]
Message-ID: <0FXK00LCQYYN5Y@la-la.cambridgesiliconradio.com> (raw)
In-Reply-To: "Your message of Wed, 12 Jul 2000 12:29:43 +0200." <200007121029.MAA21938@beta.informatik.hu-berlin.de>
Sven wrote:
> There is still something fishy, though. A string like `ls (#i)foo' is
> broken into `ls' and `(#i)foo', but `[[ (#i)foo ]]' is broken into
> `[[', `(', `#i', `)', ... I haven't found out where and why this
> happens yet.
I can partly answer that. There's a context dependency in conditions,
because a `(' may introduce the start of a pattern, as here, or it may
introduce the start of a group. Luckily, the former only happens when we
are expecting an argument to a test (you can't have patterns on the left of
an `=' or `!=', otherwise the issue would have been unresolvable) and the
latter when we are expecting a complete test, so we can check. In your
example, `(' should indeed be a single token introducing a group, so the
parsing is correct. I don't know exactly what happens on the right of an
`=', but it's possible that in that case, too, the `(' is lexed before we
decide and the string put together later, but it may also be normal.
--
Peter Stephenson <pws@cambridgesiliconradio.com>
Cambridge Silicon Radio, Unit 300, Science Park, Milton Road,
Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070
next prev parent reply other threads:[~2000-07-12 10:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-07-12 10:29 Sven Wischnowsky
2000-07-12 10:40 ` Peter Stephenson [this message]
2000-07-12 15:14 ` Bart Schaefer
-- strict thread matches above, loose matches on Subject: below --
2000-07-12 10:47 Sven Wischnowsky
2000-07-12 11:11 ` Peter Stephenson
2000-07-12 16:57 ` Peter Stephenson
2000-07-12 18:41 ` Bart Schaefer
2000-07-12 8:25 Bart Schaefer
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=0FXK00LCQYYN5Y@la-la.cambridgesiliconradio.com \
--to=pws@cambridgesiliconradio.com \
--cc=zsh-workers@sunsite.auc.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).