From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: pws@ifh.de (Peter Stephenson)
Cc: zsh-workers@math.gatech.edu
Subject: Re: Here docs
Date: Thu, 1 Aug 1996 16:07:40 +0200 (MET DST) [thread overview]
Message-ID: <199608011407.QAA27343@bolyai.cs.elte.hu> (raw)
In-Reply-To: <199608011349.PAA09906@hydra.ifh.de> from Peter Stephenson at "Aug 1, 96 03:49:39 pm"
Peter wrote:
> I expect Zoltan's already fixed this, but anyway...
Yes :-).
> > In this case, the backslash in the input will behave as the
> > backslash inside double-quotes (see Section 2.2.3) However, the
> > double-quote character (") will not be treated specially within a
> > here-document, except when the double-quote appears within $(), ``, or
> > ${}.
>
> That's clear enough for here documents... the question is what should
> happen at other times when zsh is parsing something in the same way.
> This is usually when tokenising a string that hadn't already been
Here is my patch, a bit different from yours. It fixes some other
inconsistencies and it also handles " in ${...} as reuired above. When I
read POSIX I was pleased to know that here ducuments should be parsed the
same way as double-quoted strings, and relaxed knowing that zsh does
exactly that. And indeed the problem was not really in the here-document
code. I did not notice this problem because configure coming with zsh
always ran fine.
Zoltan
*** Src/lex.c 1996/07/24 14:39:19 2.40
--- Src/lex.c 1996/08/01 13:47:44
***************
*** 996,1008 ****
while (((c = hgetc()) != endchar || bct ||
(math && ((pct > 0) || (brct > 0))) ||
intick) && !lexstop) {
switch (c) {
case '\\':
c = hgetc();
! if (c != '\n')
! add(c == '$' || c == '\\' || (c == '}' && !intick && bct) ||
! c == '\"' || c == '`' ? Bnull : '\\');
! else if (sub || unset(CSHJUNKIEQUOTES) || endchar != '"')
continue;
break;
case '\n':
--- 996,1015 ----
while (((c = hgetc()) != endchar || bct ||
(math && ((pct > 0) || (brct > 0))) ||
intick) && !lexstop) {
+ cont:
switch (c) {
case '\\':
c = hgetc();
! if (c != '\n') {
! if (c == '$' || c == '\\' || (c == '}' && !intick && bct) ||
! c == endchar || c == '`')
! add(Bnull);
! else {
! /* lexstop is implicitely handled here */
! add('\\');
! goto cont;
! }
! } else if (sub || unset(CSHJUNKIEQUOTES) || endchar != '"')
continue;
break;
case '\n':
***************
*** 1092,1098 ****
err = (!brct-- && math);
break;
case '"':
! if (intick || !endchar)
break;
if (bct) {
add(Dnull);
--- 1099,1105 ----
err = (!brct-- && math);
break;
case '"':
! if (intick || (!endchar && !bct))
break;
if (bct) {
add(Dnull);
next prev parent reply other threads:[~1996-08-01 14:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-31 21:11 Announcement draft Zoltan Hidvegi
1996-07-31 22:15 ` Zefram
1996-08-01 6:36 ` Bas V. de Bakker
1996-08-01 8:31 ` Peter Stephenson
1996-08-01 9:04 ` Running zsh as sh (Was: Announcement draft) Bas V. de Bakker
1996-08-01 9:10 ` Announcement draft Andrej Borsenkow
1996-08-01 13:49 ` Here docs Peter Stephenson
1996-08-01 14:07 ` Zoltan Hidvegi [this message]
1996-08-01 16:27 ` More Configure problems Peter Stephenson
1996-08-01 17:40 ` Peter Stephenson
1996-08-01 17:55 ` Zoltan Hidvegi
1996-08-01 21:03 ` Zoltan Hidvegi
1996-08-01 23:30 ` Zoltan Hidvegi
1996-08-02 8:32 ` Peter Stephenson
1996-08-02 10:03 ` Andrej Borsenkow
1996-08-02 13:29 ` Zoltan Hidvegi
1996-08-02 1:03 ` Zefram
1996-08-01 14:42 ` Announcement draft Zoltan Hidvegi
1996-08-08 15:13 ` sh compatibility again :-> Andrej Borsenkow
1996-08-12 2:18 ` Zoltan Hidvegi
1996-08-12 4:36 ` Bart Schaefer
1996-08-12 5:00 ` Zefram
1996-08-12 6:01 ` Bart Schaefer
1996-08-12 6:34 ` Bart Schaefer
1996-08-12 6:20 ` Andrej Borsenkow
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=199608011407.QAA27343@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=pws@ifh.de \
--cc=zsh-workers@math.gatech.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.
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).