From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id BAA29024 for ; Tue, 16 Jul 1996 01:35:46 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id LAA15732; Mon, 15 Jul 1996 11:15:15 -0400 (EDT) Resent-Date: Mon, 15 Jul 1996 11:15:15 -0400 (EDT) Message-Id: <199607151512.LAA01837@spacely.icd.teradyne.com> X-Mailer: exmh version 1.6.7 5/3/96 To: zsh-workers@math.gatech.edu Subject: Re: Incompatibility in zsh-3.0-pre3 ? In-reply-to: pws's message of Mon, 15 Jul 1996 10:42:54 +0200. <199607150842.KAA05023@hydra.ifh.de> reply-to: acs@world.std.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 15 Jul 1996 11:12:22 -0400 From: Vinnie Shelton Resent-Message-ID: <"h6iIh2.0.lr3.22cwn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1655 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu pws@ifh.de said: > This is due to the change that {, }, and [[ are treated as `reserved > words' --- which basically means they have to appear separately on > the command line. This is for compatibility (repeat mantra 57 times > :-/). I just want to go on record as stating that I think this is really NOT a good thing. IMO, *way* too many scripts and functions are going to break. Bart's example is a good one: : grind Mon 15 11:04; echo $ZSH_VERSION 3.0-pre2 : grind Mon 15 11:04; [[-z $foo]] && echo foo is not set foo is not set : grind Mon 15 11:05; echo $ZSH_VERSION 3.0-pre3 : grind Mon 15 11:05; [[-z $foo]] && echo foo is not set zsh: bad pattern: [[-z Big picture questions: How can we have major changes like this shortly before a release? What's the timeframe for the 3.0 release? When do we stop making incompatible changes? --vin