zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: array prepend
Date: Sun, 13 Jan 2013 17:50:23 -0800	[thread overview]
Message-ID: <130113175023.ZM5855@torch.brasslantern.com> (raw)
In-Reply-To: <20130113185141.4394d532@pws-pc.ntlworld.com>

[redirected to -workers]

On Jan 13,  6:51pm, Peter Stephenson wrote:
} Subject: Re: array prepend
}
} On Sat, 12 Jan 2013 02:38:13 +0100
} Oliver Kiddle <okiddle@yahoo.co.uk> wrote:
} > If you dig out the mailing list discussion from when += was added
} > you'll see that the main reason there isn't a prepend is that we
} > couldn't think of suitable syntax that would be backward compatible.
} 
} I was thinking about /=.  I started looking at it once but got bored
} with all the varieties of parameter type.

Hrm, I'm not exactly excited by that choice, /= implies some sort of
division rather than union.

} > -= for example
} > isn't possible because a - character is valid in an identifier.

Thinking again, I'm not sure that's the reason.  There doesn't seem to
be any syntactic reason to exclude -= (it doesn't parse now); rather,
=+ doesn't work because a + character is valid in the parameter value,
but I think -= was rejected on the same implied-semantics grounds that
I just raised for /=.

What about a special case for empty brackets?  VAR[] is not currently
a valid identifier even though e.g. VAR[*] is.

 	VAR[]=(this is prepended)
 	VAR[]+=(this is appended)
 	VAR+=(short for 'VAR[]+=')


       reply	other threads:[~2013-01-14  1:50 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50EFB80D.30002@sergio.spb.ru>
     [not found] ` <22417.1357954693@thecus.kiddle.eu>
     [not found]   ` <20130113185141.4394d532@pws-pc.ntlworld.com>
2013-01-14  1:50     ` Bart Schaefer [this message]
2013-01-14 15:48       ` Oliver Kiddle
2013-01-17  5:02         ` Bart Schaefer
2013-01-14 18:36       ` Greg Klanderman
2013-01-17  5:00         ` Bart Schaefer
2013-01-17 14:52           ` Greg Klanderman
2013-01-17 15:49             ` Bart Schaefer
2013-01-19  7:53             ` Han Pingtian
2013-01-19 16:41               ` Bart Schaefer
2013-01-20 11:08                 ` Han Pingtian

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=130113175023.ZM5855@torch.brasslantern.com \
    --to=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).