From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: triviality regarding $# counts
Date: Sun, 14 Apr 2024 07:47:48 -0700 [thread overview]
Message-ID: <2a3cc24f-f006-4889-aaaa-2715b8b1d7cd@eastlink.ca> (raw)
In-Reply-To: <CAA=-s3zAWkKq5JsTHhKFsLYFN57jTb7GtHTAoGMKdHWj8bshEA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
On 2024-04-14 07:06, Mark J. Reed wrote:
>
> What? No. Why do you keep bringing (f) into this? That flag has
> nothing to do with copying; in fact it intentionally changes things:
> anywhere there used to be a single string containing a newline,you get
> two strings instead.
% hhh=( "${(@f)iii}" )
% typeset -p hhh; typeset -p iii
typeset -a hhh=( 'abc\ndef\nghi' )
typeset iii='abc\ndef\nghi'
... newlines still there. One element.
Besides it worked as I showed.
>
> But if you drop the f, you do get your Xerox copy:
>
> % fff=( "${(@)ddd}" )
>
... so far so good with tests. The (f) seems not to have removed
anything -- I was sure it did, yesterday :( -- but that was then. But
yours seems to work and it's simpler, more intuitive. The (f) does not
seem to be missed, either. And to think that just yesterday I thought I
had this all sorted.
> Would it be nicer if you could just do *fff=$ddd* and not have to
> include the parens and quotes and @? Sure. You could even make a case
> that it /should /work that way, since we're in Zshland where *$ddd*
> expands to the whole array instead of a single element. But that's not
> the way assignment works. Though, as I said, if the array has no empty
> elements, you can get away with just *fff=($ddd)*.
'IF' ... what I'm wanting is some universal copy that has no gotchas.
BTW, just philosophically speaking, the parens are an interesting
question. Whereas I'd say that a copy is a copy is a copy:
aaa=$bbb
... so whatever bbb may happen to be, aaa will become the same. But if
aaa is a scalar, should it be promoted 'silently' ? Seems to me the
parens are explicit that aaa will become an array so I like them. One
can never be too clear as to what's happening.
cut
[-- Attachment #2: Type: text/html, Size: 3212 bytes --]
next prev parent reply other threads:[~2024-04-14 14:48 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-11 0:56 Ray Andrews
2024-04-12 4:55 ` Lawrence Velázquez
2024-04-12 14:48 ` Ray Andrews
2024-04-12 19:09 ` Bart Schaefer
2024-04-13 1:13 ` Ray Andrews
2024-04-13 1:33 ` Mark J. Reed
2024-04-13 2:28 ` Ray Andrews
2024-04-13 3:25 ` Lawrence Velázquez
2024-04-13 14:37 ` Ray Andrews
2024-04-13 15:14 ` Ray Andrews
2024-04-13 17:19 ` Mark J. Reed
2024-04-13 17:27 ` Mark J. Reed
2024-04-13 18:08 ` Ray Andrews
2024-04-13 19:45 ` Bart Schaefer
2024-04-13 20:36 ` Ray Andrews
2024-04-13 21:01 ` Bart Schaefer
2024-04-14 0:28 ` Ray Andrews
2024-04-14 0:30 ` Lawrence Velázquez
2024-04-14 3:26 ` Ray Andrews
2024-04-14 3:49 ` Lawrence Velázquez
2024-04-14 4:57 ` Bart Schaefer
2024-04-14 13:24 ` Ray Andrews
2024-04-14 13:35 ` Roman Perepelitsa
2024-04-14 14:06 ` Ray Andrews
2024-04-14 14:15 ` Roman Perepelitsa
2024-04-14 14:53 ` Ray Andrews
2024-04-14 15:11 ` Mark J. Reed
2024-04-14 16:23 ` Ray Andrews
2024-04-14 14:06 ` Mark J. Reed
2024-04-14 14:47 ` Ray Andrews [this message]
2024-04-14 14:59 ` Mark J. Reed
2024-04-14 15:51 ` Bart Schaefer
2024-04-14 17:22 ` Ray Andrews
2024-04-14 17:42 ` Mark J. Reed
2024-04-14 18:24 ` Bart Schaefer
2024-04-14 22:00 ` Ray Andrews
2024-04-13 20:11 ` Mark J. Reed
2024-04-13 20:53 ` Bart Schaefer
2024-04-14 0:19 ` Ray Andrews
2024-04-13 1:35 ` 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=2a3cc24f-f006-4889-aaaa-2715b8b1d7cd@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-users@zsh.org \
/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).