zsh-workers
 help / color / mirror / code / Atom feed
From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: Adam Spiers <adam@spiers.net>,
	Zsh hackers list <zsh-workers@sunsite.auc.dk>
Subject: Re: comments break \ at end of line
Date: Fri, 25 Aug 2000 16:23:52 +0000	[thread overview]
Message-ID: <1000825162352.ZM12107@candle.brasslantern.com> (raw)
In-Reply-To: <20000825153830.C22595@thelonious.new.ox.ac.uk>

On Aug 25,  3:38pm, Adam Spiers wrote:
} Subject: Re: comments break \ at end of line
}
} I'm suggesting that, in the case of the function, it turns it into
} `echo hello, world', and in second case, it expects another line of
} input, just as if you hadn't entered the comment line.  After all,
} comment lines are supposed to be ignored, aren't they?

No, comment *lines* aren't supposed to be ignored.  *Comments* are
supposed to be ignored.  A comment is everything from the # up to BUT
NOT INCLUDING the newline.

If the comment included the newline, all sorts of parsing would go wrong:

if test foo # comment
then

Would become:

if test foo then

Which is certainly not what you meant.

A comment beginning in the first column is treated the same as a comment
beginning in any other column, which I think IS what you want; you don't
want the syntax of your program changed by the introduction of leading
whitespace, do you?

-- 
Bart Schaefer                                 Brass Lantern Enterprises
http://www.well.com/user/barts              http://www.brasslantern.com

Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net   


  parent reply	other threads:[~2000-08-25 16:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-08-24 21:29 Adam Spiers
2000-08-25 10:32 ` Peter Stephenson
2000-08-25 14:38   ` Adam Spiers
2000-08-25 15:58     ` Andrej Borsenkow
2000-08-25 16:23     ` Bart Schaefer [this message]
2000-08-25 10:35 Sven Wischnowsky

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1000825162352.ZM12107@candle.brasslantern.com \
    --to=schaefer@candle.brasslantern.com \
    --cc=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).