zsh-workers
 help / color / mirror / code / Atom feed
From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
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 19:58:09 +0400	[thread overview]
Message-ID: <000001c00ead$44065290$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <20000825153830.C22595@thelonious.new.ox.ac.uk>

> 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?

That is exactly what happens currently - everything from `#' up to the next
EOL is ignored.


This seems far
> more sensible behaviour to me: a) it's useful to be able to
> intersperse comments with continuation lines,

No, I am against it. It will turn into a nightmare.

echo foo \
#
# ... 57 lines of comments
#
echo bar

How do you like it?
                                                                      and b)
if you didn't
> want the continuation happening, you wouldn't have included the
> backslashes in the first place.
>

It is not a continuation. It is simply removing of EOL no more no less (and so
it is documented). Yes, for all practical purposes it is the same as
continuation ...

> > I don't see how you can turn it
> > off without writing a completely new (= bugridden) way of lexing.
>
> As is probably already obvious, I'm fairly ignorant of zsh's lexing
> and parsing.  At what stage do comments get dropped?  I would have
> thought that if they were dropped earlier on that this would achieve
> what I want, but I'm just guessing.
>

But I just realised. In case of

echo foo \
# comment
bar

how do you want to indicate, that `bar' is not a comment? I mean

echo foo \
#comment \
bar

is the same as

echo foo #comment bar

that makes bar be happily ignored. The above change is trivial,  but gains you
nothing. Anything else, I agree, is too error prone.

-andrej


  reply	other threads:[~2000-08-25 15:58 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 [this message]
2000-08-25 16:23     ` Bart Schaefer
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='000001c00ead$44065290$21c9ca95@mow.siemens.ru' \
    --to=andrej.borsenkow@mow.siemens.ru \
    --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).