Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Incompatibility in zsh-3.0-pre3 ?
- X-seq: zsh-workers 1655
- From: Vinnie Shelton <shelton@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxxxxxxx
- Subject: Re: Incompatibility in zsh-3.0-pre3 ?
- Date: Mon, 15 Jul 1996 11:12:22 -0400
- In-reply-to: pws's message of Mon, 15 Jul 1996 10:42:54 +0200. <199607150842.KAA05023@xxxxxxxxxxxx>
- Reply-to: acs@xxxxxxxxxxxxx
pws@xxxxxx 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author