* field splitting behavior
@ 2001-11-27 19:04 Paul Lew - remove nospam when reply
2001-11-27 19:21 ` Zefram
0 siblings, 1 reply; 3+ messages in thread
From: Paul Lew - remove nospam when reply @ 2001-11-27 19:04 UTC (permalink / raw)
To: zsh-users
Take a look at the following:
> var='foo:bar'
> echo ${(@)${(s/:/)var}[1]}
foo
> var='foobar'
> echo ${(@)${(s/:/)var}[1]}
f
So why it did field splitting on each character when there is no
separator ':' found? I would expect 'foobar' on the output.
Thanks in advance..
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: field splitting behavior
2001-11-27 19:04 field splitting behavior Paul Lew - remove nospam when reply
@ 2001-11-27 19:21 ` Zefram
2001-11-28 10:30 ` Peter Stephenson
0 siblings, 1 reply; 3+ messages in thread
From: Zefram @ 2001-11-27 19:21 UTC (permalink / raw)
To: zsh-users
Paul Lew wrote:
>> var='foobar'
>> echo ${(@)${(s/:/)var}[1]}
>f
>
>So why it did field splitting on each character when there is no
>separator ':' found? I would expect 'foobar' on the output.
The result of the splitting is a single word "foobar", as you expect.
This is then treated as a scalar, not an array, and so the [1] extracts
the first character, instead of the first element. The (@) doesn't do
what you think it does (it only has an effect where double quotes are
used). I don't see any easy way to force the result of a ${(s...)...}
to be treated as an array, so I'll have to leave that to the expansion
wizards.
-zefram
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: field splitting behavior
2001-11-27 19:21 ` Zefram
@ 2001-11-28 10:30 ` Peter Stephenson
0 siblings, 0 replies; 3+ messages in thread
From: Peter Stephenson @ 2001-11-28 10:30 UTC (permalink / raw)
To: Zsh users list
Zefram wrote:
> Paul Lew wrote:
> >> var='foobar'
> >> echo ${(@)${(s/:/)var}[1]}
> >f
> >
> >So why it did field splitting on each character when there is no
> >separator ':' found? I would expect 'foobar' on the output.
>
> The result of the splitting is a single word "foobar", as you expect.
> This is then treated as a scalar, not an array, and so the [1] extracts
> the first character, instead of the first element. The (@) doesn't do
> what you think it does (it only has an effect where double quotes are
> used). I don't see any easy way to force the result of a ${(s...)...}
> to be treated as an array, so I'll have to leave that to the expansion
> wizards.
I can only think of the gross hack
print ${${(s/:/):-${var}:rubbish}[1]}
which extends the string to make sure it produces an array. It's somewhat
inconsistent that you sometimes get a scalar and sometimes an array.
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR Ltd., Science Park, Milton Road,
Cambridge, CB4 0WH, UK Tel: +44 (0)1223 392070
**********************************************************************
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.
**********************************************************************
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-11-28 10:31 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-11-27 19:04 field splitting behavior Paul Lew - remove nospam when reply
2001-11-27 19:21 ` Zefram
2001-11-28 10:30 ` Peter Stephenson
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).