From: Felipe Contreras <felipe.contreras@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Daniel Shahaf <d.s@daniel.shahaf.name>,
Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Bug with unset variables
Date: Sat, 28 Nov 2020 06:05:12 -0600 [thread overview]
Message-ID: <CAMP44s16Gd_Qgs5bvYF3NgYrrdSkb5r3ZPJQ1aA1dvKv4xNpRA@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7awR=pODg+mcHKvssPyWPPhDeOb-TMG3B336bfeLOKf=w@mail.gmail.com>
On Fri, Nov 27, 2020 at 6:25 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> On Fri, Nov 27, 2020 at 3:38 PM Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
> >
> > The best way to move forward would be to write a patch against the Test/
> > directory that specifies the proposed behaviour. Use the "f" flag so
> > all newly-added tests will run, rather than just the first.
>
> There are existing tests that specifically check for the current
> behavior, so it's not as if this were simply overlooked.
>
> To write the proposed new test cases, we need to decide (this list may
> not be all-inclusive):
Yeah, I agree it's not as straightforward as it initially seemed.
I can write a test case for what I think should be the desired
behavior in the typical case: "typeset var" does *not* set var to an
empty string.
But that ignores most of the discussion that has already happened
here, and it seems in the Austin CSRG.
I bet it's possible to write the code that passes the above test-case,
but ten years from now--and if not, it will be twenty years from
now--somebody will try to add "local" to POSIX again, and zsh will
still be an inconsistent state.
Personally, I would rather attempt to do it right today, than add a
hack that sort of does what I initially wanted.
Maybe we are wasting time chasing multiple tails, but maybe we are
onto something.
Considering that POSIX hasn't managed to crack the problem after
essentially half a century, maybe a couple of mails in this mailing
list couldn't hurt.
When the solution requires creativity, you just can't know where it
could come from.
Cheers.
--
Felipe Contreras
next prev parent reply other threads:[~2020-11-28 12:05 UTC|newest]
Thread overview: 53+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-11 15:57 Felipe Contreras
2020-11-11 16:13 ` Roman Perepelitsa
2020-11-11 16:56 ` Felipe Contreras
2020-11-11 17:02 ` Roman Perepelitsa
2020-11-11 18:03 ` Felipe Contreras
2020-11-11 18:16 ` Roman Perepelitsa
2020-11-11 20:42 ` Felipe Contreras
2020-11-12 0:20 ` Mikael Magnusson
2020-11-12 1:10 ` Felipe Contreras
2020-11-12 8:45 ` Roman Perepelitsa
2020-11-12 10:47 ` Peter Stephenson
2020-11-12 18:48 ` Bart Schaefer
2020-11-12 19:49 ` Felipe Contreras
2020-11-12 18:46 ` Felipe Contreras
2020-11-12 19:10 ` Roman Perepelitsa
2020-11-12 21:08 ` Felipe Contreras
2020-11-13 8:51 ` Roman Perepelitsa
2020-11-14 0:52 ` Felipe Contreras
2020-11-14 5:41 ` Roman Perepelitsa
2020-11-16 19:41 ` Felipe Contreras
2020-11-16 20:22 ` Roman Perepelitsa
2020-11-17 20:28 ` Felipe Contreras
2020-11-18 22:45 ` Daniel Shahaf
2020-11-22 1:20 ` Felipe Contreras
2020-11-23 4:00 ` Daniel Shahaf
2020-11-23 6:18 ` Felipe Contreras
2020-11-19 2:59 ` Bart Schaefer
2020-11-22 1:50 ` Felipe Contreras
2020-11-17 20:54 ` Bart Schaefer
2020-11-22 1:49 ` Felipe Contreras
2020-11-23 6:48 ` Bart Schaefer
2020-11-23 7:26 ` Felipe Contreras
2020-11-23 20:26 ` Bart Schaefer
2020-11-23 23:39 ` Felipe Contreras
2020-11-24 0:52 ` Bart Schaefer
2020-11-25 8:46 ` Felipe Contreras
2020-11-27 15:44 ` Daniel Shahaf
2020-11-27 20:49 ` Felipe Contreras
2020-11-27 20:59 ` Daniel Shahaf
2020-11-27 21:33 ` Bart Schaefer
2020-11-27 23:37 ` Daniel Shahaf
2020-11-27 23:45 ` Bart Schaefer
2020-11-28 0:24 ` Bart Schaefer
2020-11-28 7:32 ` Bart Schaefer
2020-11-28 12:05 ` Felipe Contreras [this message]
2020-11-12 19:26 ` Bart Schaefer
2020-11-12 21:48 ` Felipe Contreras
2020-11-13 22:17 ` Bart Schaefer
2020-11-14 0:58 ` Felipe Contreras
2020-11-11 18:36 ` Bart Schaefer
2020-11-11 21:08 ` Felipe Contreras
2020-11-11 17:02 ` Peter Stephenson
2020-11-11 18:05 ` Felipe Contreras
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=CAMP44s16Gd_Qgs5bvYF3NgYrrdSkb5r3ZPJQ1aA1dvKv4xNpRA@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=schaefer@brasslantern.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).