From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-35535-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 16616 invoked by alias); 19 Jun 2015 18:55:01 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 35535
Received: (qmail 21859 invoked from network); 19 Jun 2015 18:55:00 -0000
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW,
	RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL autolearn=ham autolearn_force=no
	version=3.4.0
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:from:message-id:date:in-reply-to:comments
         :references:to:subject:mime-version:content-type;
        bh=GObnlGui+ZkUflQM3vwIA/cPJHkNPpbJFcgpRIX68YY=;
        b=Dqlar/8Og3vRU3utzwB3P1Prba//PbXcGu9FlrKXH+VZ9jzALmn9G0j2ncsY0nMoid
         3wZ+sx9kF7ZMJ4Vd3msr3SPn/TTaA1C8kQGhQAp2LiSO9aOZrIU/5i26IL34xLhWDAuv
         E9L10XN0oZuACQG6rZsPX5+I3YhI1h5ETqEOteSVDo1hIVYCVsG1IFUJMaxUX2NzXDKO
         1VGH7n8O2V7TK5B1mc4l51Lcv7plY2LEbV5pdD91M3WYsbp/8sqE93yyUSOXMAJ5u169
         Wh+IpVu9+AFlLC0/I9JhSxxmYaWZE2mtaH3g/2xebZUAqjs8E65JH8DlQ1nO6TLywMfi
         mcjQ==
X-Gm-Message-State: ALoCoQnThBURZ5/V8k3aoFcvajRn3k7jpWoxK/xoGYzLtnoMrFeWLm9NpG3eSNY5cst3Oqj39DQX
X-Received: by 10.202.63.212 with SMTP id m203mr14018156oia.35.1434740098463;
        Fri, 19 Jun 2015 11:54:58 -0700 (PDT)
From: Bart Schaefer <schaefer@brasslantern.com>
Message-Id: <150619115454.ZM4290@torch.brasslantern.com>
Date: Fri, 19 Jun 2015 11:54:54 -0700
In-Reply-To: <20150619150624.3368cd00@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
        "Re: Typeset with array" (Jun 19,  3:06pm)
References: <5578996E.3080700@thequod.de> 
	<150610191427.ZM30841@torch.brasslantern.com> 
	<5579C247.1060800@thequod.de> 
	<150611183639.ZM32247@torch.brasslantern.com> 
	<20150612094237.338f79d5@pwslap01u.europe.root.pri> 
	<20150619123930.2688d9e3@pwslap01u.europe.root.pri> 
	<20150619150624.3368cd00@pwslap01u.europe.root.pri>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: "Zsh Hackers' List" <zsh-workers@zsh.org>
Subject: Re: Typeset with array
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii

On Jun 19,  3:06pm, Peter Stephenson wrote:
}
} - The new interface "fixes" the old behaviour
} 
}   typeset noktfoo=`echo noktarg1 noktarg2`
} 
} so that this now assigns a scalar to noktfoo with no wordsplitting.
} This is certainly correct for the interface we are trying to implement,
} because it's what bash does.  However, it was previously controlled by
} KSH_TYPESET.  What's the right way to do it from now on?

Does this raise a larger question of whether the reserved word should be
enabled by default in "zsh mode"?

If this only affects the reserved word interface and the reserved word
has to be explicitly enabled (by "emulate" or "enable") then there's no
issue.

OTOH it would be nice to have the reserved word on by default.  Using
array assignment syntax in the arguments of typeset would generally have
been a syntax or globbing error in the past, so this word splitting is
the primary place where a valid statement might change its semantics.

} kludge in the old behaviour with NO_KSH_TYPESET if it seems desirable,

Are there any other practical differences between KSH_TYPESET and having
the reserved word enabled?

} though logically that shouldn't really control the reserved word
} interface which should parse consistently.

Agreed.