From: haahr@adobe.com
To: schwartz@groucho.cs.psu.edu
Cc: rc mailing list <rc@archone.tamu.edu>
Subject: Re: comments, newlines
Date: Wed, 11 Mar 1992 11:27:00 -0600 [thread overview]
Message-ID: <9203111727.AA04643@utopia.adobe.com> (raw)
the reason that
x=(1 \
# 2 \
3)
doesn't work is straightforward interpretation of rc's rules for continued
lines and comments. the first \+newline sequence results in the parser
seeing
x=(1 # 2 \
3)
which seems reasonable. now the question becomes, ``are backslash-newline
sequences in comments ignored or treated as continuation sequences?'' rc
currently implements comments by ignoring *everything* until the end of
line. the simplicity of this rule argues for not changing it.
two further comments:
i don't find the ability to insert a comment in the middle of a
sequence of lines continued with \ important
i have no idea what td's rc does for this
next reply other threads:[~1992-03-12 10:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1992-03-11 17:27 haahr [this message]
1992-03-12 22:05 ` David J. Fiander
1992-03-13 10:14 ` John Mackin
1992-03-13 22:44 ` Dave Mason
-- strict thread matches above, loose matches on Subject: below --
1992-03-14 19:39 Emin G. Sirer
1992-03-15 23:31 ` James Matthew Farrow
1992-03-15 17:54 ` schwartz
1992-03-11 7:19 schwartz
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=9203111727.AA04643@utopia.adobe.com \
--to=haahr@adobe.com \
--cc=rc@archone.tamu.edu \
--cc=schwartz@groucho.cs.psu.edu \
/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.
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).