Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [PATCH] Documentation on (A) Create array parameter
- X-seq: zsh-workers 40618
- From: Sebastian Gniazdowski <psprint2@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: [PATCH] Documentation on (A) Create array parameter
- Date: Wed, 22 Feb 2017 12:47:48 -0800
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.com; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=/PdDprU8+nweHiQP7eYCnIbJ3w c=; b=XV4W2Bu6KS9SCv4nZM96i6FZXTskxxfYZIfcFroeNq6H8HezI/21MFlieG 4CU9NJsoaqCCTUKKuRgVGV5hauFbSsfsMYYvGZU+x5VINK4/2BrAVU/icN/eVasl weZ+qlGaQvIAyY8NjgtFlk0SZMX9DztuOOCU8uKXDNr2nyke4=
- Dkim-signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=smtpout; bh=/P dDprU8+nweHiQP7eYCnIbJ3wc=; b=LOtsmyzQwrwezqTKNnE2qe2VhijHUw5Wbo 6rTvDNVG3Ac+nL25YCu3LQtifzHwmQZ1DGzeLWtvYx9v0lip1oopnkwIvj/W+/Pb bEMm5cMkq412XbPVEd7DSf2WWdF0Em77csQovrR7xgSh/2Z9ElITb+8Ms66HktQ2 +t21EMC3w=
- In-reply-to: <170222115802.ZM18878@torch.brasslantern.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <1487763613.2941773.889107120.2750751A@webmail.messagingengine.com> <170222115802.ZM18878@torch.brasslantern.com>
On Wed, Feb 22, 2017, at 11:58 AM, Bart Schaefer wrote:
> On Feb 22, 3:40am, Sebastian Gniazdowski wrote:
> }
> } (A) completion and documentation suggest straight creation:
>
> There's no such thing as "straight creation" of a parameter; the whole
> shell model depends on dynamic scoping. Assignments *always* apply to
> any parameter that is already in scope, the only way to change that is
> by declaring the parameter with typeset/local/etc.
It's that if I have a new scope, and write "local param", I would say I
straight-create it. It will have the "oldpm" field set internally but
it's all like straight creation. If the scope is new. So I could expect
(A) will behave the same way. Use my current scope and create.
> scoping is something for a much larger context. Would it have led you
> astray if instead the paragraph said "Assign as an array parameter ..." ?
No that's fine.
--
Sebastian Gniazdowski
psprint2@xxxxxxxxxxxx
Messages sorted by:
Reverse Date,
Date,
Thread,
Author