zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Oliver Kiddle <opk@zsh.org>
Cc: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: [PATCH] declarednull: rename DECLARED to NULL
Date: Sat, 10 Apr 2021 11:56:37 -0700	[thread overview]
Message-ID: <CAH+w=7Z1ZRiTggr_Y=PdaEQ4H06t_Dq2R5PQ3fm7TOVxwwsUoQ@mail.gmail.com> (raw)
In-Reply-To: <83994-1616978678.232193@jPMH.zQZs.0I47>

On Sun, Mar 28, 2021 at 5:44 PM Oliver Kiddle <opk@zsh.org> wrote:
>
> Bart Schaefer wrote:
> > IMO the primary remaining question is
> > whether it's acceptable to make the user-visible behavior dependent on
> > the POSIX_BUILTINS option.
>
> It seems fairly self-contained and could have it's own option. typeset
> isn't a builtin. posix compatibility options aren't really improvements
> but someone might prefer this behaviour.

(I'm reading that as "typeset isn't a POSIX builtin").  There has at
least been discussion about standardizing "local" on austin-group, and
given that "local" is an alias for typeset, this (or related) behavior
might become a POSIX compatibility thing in the future.

I'm also somewhat concerned that choosing a descriptive name for a new
option is going to spawn another argument.  TYPESET_DOES_NOT_SET ?

As mentioned long ago, it could also be an emulation-mode thing,
although that makes it a lot more difficult to access at a scripting
level.

> Was there anything else outstanding like (t) output perhaps?

I believe I have dealt properly with ${(t)var}.  I'll add something to
the doc about ${emptystr[(i)]}, because that's a weird case even
without this patch.


  reply	other threads:[~2021-04-10 18:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-28 22:13 Felipe Contreras
2021-01-03  1:18 ` Bart Schaefer
2021-01-03  2:38   ` Felipe Contreras
2021-01-03 18:26     ` Bart Schaefer
2021-01-04  6:17       ` Daniel Shahaf
2021-01-04 21:57         ` Bart Schaefer
2021-01-06 16:02           ` Daniel Shahaf
2021-01-06 17:33             ` Bart Schaefer
2021-01-07 15:48               ` Daniel Shahaf
2021-01-07 22:29                 ` Bart Schaefer
2021-03-27 19:24               ` Lawrence Velázquez
2021-03-27 20:42                 ` Bart Schaefer
2021-03-29  0:44                   ` Oliver Kiddle
2021-04-10 18:56                     ` Bart Schaefer [this message]
2021-04-10 21:58                       ` Oliver Kiddle
2021-04-10 22: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='CAH+w=7Z1ZRiTggr_Y=PdaEQ4H06t_Dq2R5PQ3fm7TOVxwwsUoQ@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=opk@zsh.org \
    --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).