zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: zsh-users@zsh.org
Subject: Re: uninvited members of associative array
Date: Sat, 17 Dec 2022 13:47:49 +0100	[thread overview]
Message-ID: <CAP+y1xDvByg1j+uCLgyu+zFfQAThpbZr7OZMA3sQDBvDKH461w@mail.gmail.com> (raw)
In-Reply-To: <d5fedf1e-65b8-45d7-79cf-5d2ad5225512@eastlink.ca>

[-- Attachment #1: Type: text/plain, Size: 2499 bytes --]

it certainly is to be said that, even if the shell implements all the basic
programming constructs, it is meant for different objectives then those
that are targeted by the things one most commonly calls "programming
languages", and even among those there are many distinctions, so probably
it wouldn't be so easy to establish an exact definition that includes only
the "ideals" (whatever that means) programming languages and leaves
everything else out. That being said, I think that one should accept the
language for what it is and what is meant to be and do, and even if
something would be awesome if it was engineered with  hindsight (like array
expansion without empty string elision with a more same syntax, or by
default) it should be wise to understand what the language is or is not
before dipping too much one's arms and feets in it, reading the manual at
least a couple of times front to bottom, since someone has put the effort
to write it. At least I try to do it this way, I experiment a bit but then
I try to read everything I can before resorting to ask for help, it seems
only fair given that someone has to put aside whatever he is doing to
answer me.

Pier Paolo Grassi


Il giorno sab 17 dic 2022 alle ore 00:33 Ray Andrews <rayandrews@eastlink.ca>
ha scritto:

>
> On 2022-12-16 14:15, Bart Schaefer wrote:
> >
> > I'd appreciate a pointer to that definition, since apparently my PhD
> > in Computer Science is from too long ago to have covered it.
>
> Ha!  Sometimes hairs need to be split, and Dominik is surely correct
> that zsh and say C are very different, but to say that zsh isn't a
> programing language will be a chore to sustain.
>
> Daniel:
>
> > You mean that you wrote foo[bar] and didn't realize that was
> > a globbing syntax too?  zsh can't disable features because you don't
> > know them.
>
> This stuff is all so fundamental that it couldn't change even if
> everyone wanted it to.  Disable isn't the word I chose.  But there is
> something very unfriendly about situations where you're doing something
> with an array index -- and it obvious at least to oneself that this is a
> string thing, and then zsh zealously applies filename expansions to it
> when it has nothing whatsoever to do with files.  I don't mind being
> clobbered, that's part of learning the shell, still it isn't very
> intuitive.  Anyway I've learned the protections.   But one can want to
> do some string globbing and still hope not to have anything to do with
> filenames.
>
>
>
>

[-- Attachment #2: Type: text/html, Size: 3214 bytes --]

  reply	other threads:[~2022-12-17 12:49 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 23:48 Ray Andrews
2022-12-16  0:05 ` Lawrence Velázquez
2022-12-16  0:48   ` Ray Andrews
2022-12-16  1:29     ` Lawrence Velázquez
2022-12-16  2:09     ` Dominik Vogt
2022-12-16  2:56       ` Ray Andrews
2022-12-16  3:21         ` Lawrence Velázquez
2022-12-16  4:16           ` Ray Andrews
2022-12-16 10:05             ` Dominik Vogt
2022-12-16 14:13               ` Ray Andrews
2022-12-16 15:19                 ` Dominik Vogt
2022-12-16 19:14                   ` Ray Andrews
2022-12-16 16:30                 ` Daniel Shahaf
2022-12-16 18:21                   ` Ray Andrews
2022-12-16 19:04                     ` Dominik Vogt
2022-12-16 20:10                       ` Ray Andrews
2022-12-16 21:15                         ` Dominik Vogt
2022-12-16 21:33                           ` Bart Schaefer
2022-12-16 21:59                             ` Dominik Vogt
2022-12-16 22:15                               ` Bart Schaefer
2022-12-16 23:33                                 ` Ray Andrews
2022-12-17 12:47                                   ` Pier Paolo Grassi [this message]
2022-12-17 17:32                                     ` Ray Andrews
2022-12-17 18:10                                 ` Ray Andrews
2022-12-17 18:19                                   ` Roman Perepelitsa
2022-12-17 20:31                                     ` Ray Andrews
2022-12-17 20:49                                       ` Bart Schaefer
2022-12-17 21:07                                       ` Lawrence Velázquez
2022-12-17 21:52                                         ` Ray Andrews
2022-12-17 22:10                                           ` Bart Schaefer
2022-12-17 23:41                                             ` Daniel Shahaf
2022-12-18  0:15                                             ` Ray Andrews
2022-12-18  0:25                                               ` Daniel Shahaf
2022-12-18  2:13                                                 ` Ray Andrews
2022-12-18 20:12                                                   ` Daniel Shahaf
2022-12-18 20:26                                                     ` Bart Schaefer
2022-12-18 20:41                                                       ` Ray Andrews
2022-12-18  3:44                                               ` Lawrence Velázquez
2022-12-17 23:25                                         ` Daniel Shahaf
2022-12-16 21:33                           ` Ray Andrews
2022-12-16 20:25                       ` Daniel Shahaf
2022-12-16 21:43                         ` Dominik Vogt
2022-12-16  3:20 ` Bart Schaefer
2022-12-16  4:15   ` Ray Andrews
2022-12-16  8:12 ` Roman Perepelitsa

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=CAP+y1xDvByg1j+uCLgyu+zFfQAThpbZr7OZMA3sQDBvDKH461w@mail.gmail.com \
    --to=pierpaolog@gmail.com \
    --cc=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).