zsh-users
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@csr.com>
To: zsh-users@sunsite.dk
Subject: Re: zshexpn problem
Date: Mon, 21 Feb 2005 12:04:51 +0000	[thread overview]
Message-ID: <200502211204.j1LC4qp5013774@news01.csr.com> (raw)
In-Reply-To: <20050220060716.3a77bbb0@localhost>

Matthias Berndt wrote:
> On Sun, 20 Feb 2005 05:33:35 +0100
> Matthias Berndt <Berndt.Matthias@gmx.de> wrote:
> 
> > Hi,
> > 
> > When LVERSION=2.6.10 ... why:
> > print ${(s/./)LVERSION[2]}
> > ->

The s splitting happens late; it means the overall result of the
expansion is an array.  It doesn't mean the value is instantly turned
into an array.  (It's not evaluated simply left to right, for example.)

There are a list of rules in the manual page for the order in which an
expansion takes place at each level of nesting, and they have this order:

2. _Parameter Subscripting_
  i.e. the [2]
8. _Forced Splitting_
  i.e. the (s/./)

So actually it's not well defined what happens in this case.

Obviously, "documented" isn't the same as "clear".  The following sentence
is the key part of the documentation:

  Note that the Zsh Development Group accepts _no responsibility_ for any
  brain damage which may occur during the reading of the following rules.

> > print ${${(s/./)LVERSION}[2]}
> > -> 6
> > 
> > ... works 'correct', but is seems not very intelligent.

That's the correct, logical way to do it, in as much as zsh is ever
logical.  Generate an expression which returns an array, then apply the
subscript to that.  Then rule 1 comes into force.

1. _Nested Substitution_
     If multiple nested ${...} forms are present, substitution is
     performed from the inside outwards.  At each level, the
     substitution takes account of whether the current value is a
     scalar or an array, whether the whole substitution is in double
     quotes, and what flags are supplied to the current level of
     substitution, just as if the nested substitution were the
     outermost.
     ...

I still marvel that people complain about Perl being obscure.

-- 
Peter Stephenson <pws@csr.com>                  Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK                          Tel: +44 (0)1223 692070


**********************************************************************
This email and any files transmitted with it are confidential and
intended solely for the use of the individual or entity to whom they
are addressed. If you have received this email in error please notify
the system manager.

**********************************************************************


      reply	other threads:[~2005-02-21 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-20  4:33 Matthias Berndt
2005-02-20  5:07 ` Matthias Berndt
2005-02-21 12:04   ` 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=200502211204.j1LC4qp5013774@news01.csr.com \
    --to=pws@csr.com \
    --cc=zsh-users@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).