From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 25377 invoked from network); 25 Aug 2000 10:36:29 -0000 Received: from sunsite.auc.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 25 Aug 2000 10:36:29 -0000 Received: (qmail 19132 invoked by alias); 25 Aug 2000 10:35:32 -0000 Mailing-List: contact zsh-workers-help@sunsite.auc.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 12697 Received: (qmail 19119 invoked from network); 25 Aug 2000 10:35:29 -0000 Date: Fri, 25 Aug 2000 12:35:19 +0200 (MET DST) Message-Id: <200008251035.MAA12833@beta.informatik.hu-berlin.de> From: Sven Wischnowsky To: zsh-workers@sunsite.auc.dk In-reply-to: Peter Stephenson's message of Fri, 25 Aug 2000 11:32:46 +0100 Subject: Re: comments break \ at end of line Peter Stephenson wrote: > Adam wrote: > > % foo () { > > > echo hello, \ > > > # this is a comment > > > world > > > } > > % foo > > hello, > > foo:3: command not found: world > > > > which is the same issue as > > > > % echo hello, \ > > > # comment > > hello, > > > > This may be intentional, but if so, it strikes me as a rather > > undesirable feature, or at least one which you should be able to turn > > off. > > I don't really see how it could be any different. The `\' just skips the > newline, turning the line into `echo hello, # this is a comment'. `\' > never forces it into any different state of parsing, it only escapes the > next character. What are you suggesting? I don't see how you can turn it > off without writing a completely new (= bugridden) way of lexing. And the /bin/sh, ksh and bash here behave the same. Bye Sven -- Sven Wischnowsky wischnow@informatik.hu-berlin.de