From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 15822 invoked from network); 15 May 2000 10:01:58 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 15 May 2000 10:01:58 -0000 Received: (qmail 797 invoked by alias); 15 May 2000 10:01:52 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11366 Received: (qmail 790 invoked from network); 15 May 2000 10:01:52 -0000 Date: Mon, 15 May 2000 11:01:24 +0100 From: Peter Stephenson Subject: Re: ${-str} In-reply-to: "Your message of Mon, 15 May 2000 11:28:52 +0200." <200005150928.LAA14829@beta.informatik.hu-berlin.de> To: zsh-workers@sunsite.auc.dk (Zsh hackers list) Message-id: <0FUL00EFKIICVF@la-la.cambridgesiliconradio.com> Content-transfer-encoding: 7BIT Sven wrote: > Geoff Wing wrote: > > :serein% print -lr ${-str} > > :569XZfims > > % setopt norcs; echo ${-} > > 569XZfims > > Yep. The same as for the other special parameters (`${$foo}'). > Shouldn't we change this to be an error? Or do we really need this for > compatibility? I think this should be an error. This was never documented behaviour and most forms of bad parameter syntax produce complaints. -- Peter Stephenson Cambridge Silicon Radio, Unit 300, Science Park, Milton Road, Cambridge, CB4 0XL, UK Tel: +44 (0)1223 392070