From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18455 invoked from network); 1 Jun 1999 06:24:46 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 1 Jun 1999 06:24:46 -0000 Received: (qmail 196 invoked by alias); 1 Jun 1999 06:24:36 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6409 Received: (qmail 189 invoked from network); 1 Jun 1999 06:24:36 -0000 From: "Andrej Borsenkow" To: "Bart Schaefer" , "Zsh hackers list" Subject: RE: PATCH: pws-19: minor syntactic innovation Date: Tue, 1 Jun 1999 10:23:48 +0400 Message-ID: <00eb01beabf7$4edde7b0$21c9ca95@mow.siemens.ru> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0) In-Reply-To: <990531224100.ZM8919@candle.brasslantern.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 > > What's the parse of something like ${(f)"${"$(typeset)"}"} ? It doesn't > seem to be the `obvious' one -- it appears that the quoted strings are > actually nesting, because of the enclosing braces, which is something > pretty radically new. (I may be wrong.) Is this a good thing? > No. It breaks the basic shell grammar. The main problem is, it can have unexpected side effects when running in sh or ksh compatibility mode - and this is definitely bad thing. /andrej