zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane.chazelas@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: Use of == in functions
Date: Sun, 12 Jan 2020 11:21:55 +0000	[thread overview]
Message-ID: <20200112112155.yr7mgfuvjguldr6v@chaz.gmail.com> (raw)
In-Reply-To: <20200112100906.GA95942__47727.4053309642$1578823915$gmane$org@pooh.prefix.duckdns.org>

2020-01-12 11:09:06 +0100, Kusalananda Kähäri:
[...]
> == within [[ ]]
> =  within [   ]
> 
> ... just like in bash (but bash allows its built in test/[ utility to
> understand == too)
[...]

zsh's [ builtin also supports == as an alias of = (like its [[
]] construct also supports == as an alias of =), but in zsh,
=cmd is an operator that expands to the path of the cmd command,

$ echo =ls
/usr/bin/ls

so you would need:

[ a '==' b ]

(or disable the =cmd feature with set +o equals) if for some
reason you wanted to use the non-standard == in place of =.

Just like you need

[ a '=~' regex ]

for regex matching.

And

[ a '<' b ]

to compare strings lexically as < is also a redirection
operator.

Now, as none of <, ==, =~ are standard [ operators (so sh
compatibility is no longer a good reason to use the "["
command), you might as well use the ksh-style [[...]] construct
which doesn't have this kind of issue:

[[ a =~ b ]], [[ a < b ]], [[ a == b ]] are all fine (but then
again, there's no need to double the =. == is an operator that
is needed in languages where there's a need to disambiguate
between assignment and equality comparison, but inside [[...]]
(as opposed to ((...)) for instance), there's no assignment)


-- 
Stephane


           reply	other threads:[~2020-01-12 11:29 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <20200112100906.GA95942__47727.4053309642$1578823915$gmane$org@pooh.prefix.duckdns.org>]

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=20200112112155.yr7mgfuvjguldr6v@chaz.gmail.com \
    --to=stephane.chazelas@gmail.com \
    --cc=zsh-workers@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).