From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7672 invoked from network); 27 May 2000 04:02:26 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 27 May 2000 04:02:26 -0000 Received: (qmail 11621 invoked by alias); 27 May 2000 04:02:17 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 11604 Received: (qmail 11607 invoked from network); 27 May 2000 04:02:16 -0000 From: "Bart Schaefer" Message-Id: <1000527040205.ZM8671@candle.brasslantern.com> Date: Sat, 27 May 2000 04:02:04 +0000 In-Reply-To: <0FV6007MP80O0S@la-la.cambridgesiliconradio.com> Comments: In reply to Peter Stephenson "PATCH: (very) bad syntax error checking" (May 26, 3:24pm) References: <0FV6007MP80O0S@la-la.cambridgesiliconradio.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Peter Stephenson , zsh-workers@sunsite.auc.dk (Zsh hackers list) Subject: Re: PATCH: (very) bad syntax error checking MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On May 26, 3:24pm, Peter Stephenson wrote: } Subject: PATCH: (very) bad syntax error checking Patch? } It's rather late in the day to come across problems like this. } } % zsh -f ./test.zsh } ./test.zsh:3: parse error near `fi' } This line should not be executed. } } Yuk. This is the way people accidentally delete all the files on their } disks, etc. I can't believe this has always been there --- I suspect it } must be part of the parsing changes that we've somehow all missed. zagzig[233] ../zsh-2.4/src/zsh -f /tmp/foo/test.zsh /tmp/foo/test.zsh: parse error near `fi' [3] This line should not be executed. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com