From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: associative array questions
Date: Sun, 11 Dec 2022 19:09:05 -0800 [thread overview]
Message-ID: <d24b1ecb-5c3e-6d82-4d5a-d88aaa333ba2@eastlink.ca> (raw)
In-Reply-To: <CAH+w=7YTayg_D46cD2GNxTkcFz3uPeUECVm-sOb7ctQkh6LDjQ@mail.gmail.com>
On 2022-12-11 17:52, Bart Schaefer wrote:
> On Sun, Dec 11, 2022 at 2:37 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>> I should say that I thought substitution happened before assignment.
> Well, of course it does happen before the assignment is actually
> performed, but not before the parser decides that an assignment is
> (not) what is syntactically indicated.
If the learning curve wasn't about vertical I'd love to take a look
under the hood. One might cheerfully suppose that it's always obvious
when an assignment is indicated but it's not hard to believe that life
is not really so simple. Given the multiple usage of so many characters
I'm astonished that the parser could ever have been got working at all.
Agonizing accretion I expect. BTW that would also explain why that
'typedef' method you just showed me does what I want so painlessly --
the context of a typedef simplifies the parser's work.
>
next prev parent reply other threads:[~2022-12-12 3:10 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-11 17:39 Ray Andrews
2022-12-11 19:53 ` Bart Schaefer
2022-12-11 20:51 ` Ray Andrews
2022-12-11 21:41 ` Bart Schaefer
2022-12-11 22:37 ` Ray Andrews
2022-12-12 1:52 ` Bart Schaefer
2022-12-12 3:09 ` Ray Andrews [this message]
2022-12-13 3:31 ` Ray Andrews
2022-12-13 4:39 ` Bart Schaefer
2022-12-13 16:11 ` Ray Andrews
2022-12-13 16:22 ` Roman Perepelitsa
2022-12-13 20:00 ` Ray Andrews
2022-12-13 20:06 ` Roman Perepelitsa
2022-12-13 22:47 ` Ray Andrews
2022-12-13 23:06 ` Bart Schaefer
2022-12-14 1:08 ` Ray Andrews
2022-12-13 21:18 ` 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=d24b1ecb-5c3e-6d82-4d5a-d88aaa333ba2@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).