From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 6951 invoked from network); 18 Oct 1999 06:59:54 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 18 Oct 1999 06:59:54 -0000 Received: (qmail 1490 invoked by alias); 18 Oct 1999 06:59:44 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 8311 Received: (qmail 1480 invoked from network); 18 Oct 1999 06:59:43 -0000 Date: Mon, 18 Oct 1999 08:59:42 +0200 (MET DST) Message-Id: <199910180659.IAA20535@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: "Bart Schaefer"'s message of Sat, 16 Oct 1999 15:33:46 +0000 Subject: Re: "[[" (Re: PATCH: _urls again (Re: setopt localoptions noautoremoveslash)) Bart Schaefer wrote: > PWS says in http://www.ifh.de/~pws/computing/zshguide02.html#l6 > > Second aside for users of sh: you may remember that tests in sh used > a single pair of brackets, `if [ ... ]; then ...', or equivalently > as a command called test, `if test ...; then ...'. The Korn shell > was deliberately made to be different, and zsh follows that. The > reason is that `[[' is treated specially, which allows the shell to > do some extra checks and allows more natural syntax. Here on zsh-workers we could probably say what the real difference is: the parser knows about `[[ .. ]]' which should allow for faster execution (I guess this is what Peter meant by `treated specially'). `[ .. ]' can only be handled as a normal builtin. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de