zsh-workers
 help / color / mirror / code / Atom feed
From: Stephane Chazelas <stephane@chazelas.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: "Lawrence Velázquez" <vq@larryv.me>,
	"zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: Block comments ala Ray
Date: Sat, 13 Feb 2021 07:37:46 +0000	[thread overview]
Message-ID: <20210213073746.z2ruehp5jw7l55ry@chazelas.org> (raw)
In-Reply-To: <CAH+w=7adbKLjyn_qyp5V7mNnLMjiaC9JygHL-UCwbVH=JJsaSQ@mail.gmail.com>

2021-02-12 13:29:48 -0800, Bart Schaefer:
> On Fri, Feb 12, 2021 at 1:12 PM Stephane Chazelas <stephane@chazelas.org> wrote:
> >
> > But still, the comments appear not to be discarded at that point:
> >
> > $ zsh -c $'f() { echo $(echo x # comment\n); }; typeset -f f; f'
> > f () {
> >         echo $(echo x # comment
> > )
> > }
> > x
> 
> The literal text of what's contained in $(...) is retained
[...]

You're right. It looks like the contents is parsed (I suppose to
be able to handle the case x in x)... and the like inside), but
the result of that parsing seems to be discarded, and it seems
the contents of that $(...) is parsed again each time the
function is invoked.

ksh93 does appear to do the same. bash as well, but it's unclear
to me what kind of parsing it does in the first round.

See for instance:

$ bash -xc 'echo $(foo case a in a); esac)'
++ foo case a in a
bash: foo: command not found
+ echo '; esac)'
; esac)

-- 
Stephane


  reply	other threads:[~2021-02-13  7:38 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-10  6:05 Bart Schaefer
2021-02-10  6:16 ` Roman Perepelitsa
2021-02-12  6:17   ` Bart Schaefer
2021-02-12  6:26     ` Bart Schaefer
2021-02-12  6:41     ` Roman Perepelitsa
2021-02-12  7:40       ` Stephane Chazelas
2021-02-12  7:46         ` Roman Perepelitsa
2021-02-12 15:30         ` Bart Schaefer
2021-02-12 15:45           ` Stephane Chazelas
2021-02-12 16:55             ` Bart Schaefer
2021-02-12 18:16               ` Lawrence Velázquez
2021-02-12 21:02                 ` Stephane Chazelas
2021-02-12 21:12                   ` Stephane Chazelas
2021-02-12 21:29                     ` Bart Schaefer
2021-02-13  7:37                       ` Stephane Chazelas [this message]
2021-02-15 22:28               ` Daniel Shahaf
2021-02-13  4:33       ` Bart Schaefer
2021-02-15  0:42       ` Greg Klanderman
2021-02-12 15:24     ` Matthew Martin
2021-02-12 16:18       ` Bart Schaefer
2021-02-15 21:30         ` Daniel Shahaf
2021-02-15 22:35           ` Bart Schaefer
2021-02-12 20:48 ` Bart Schaefer
2021-02-13  8:35 ` Stephane Chazelas
2021-02-13  8:53   ` Stephane Chazelas
2021-02-14 20:50     ` Bart Schaefer
2021-02-14 20:15   ` Bart Schaefer
2021-02-15  0:36     ` Vincent Lefevre
2021-02-15  1:07       ` Bart Schaefer
2021-02-15  1:38         ` Vincent Lefevre
2021-02-15 17:43     ` Stephane Chazelas
2021-02-15 22:06       ` Daniel Shahaf
2021-02-15 22:39         ` Bart Schaefer
2021-02-14 20:58   ` Bart Schaefer
2021-02-16 15:30 ` Juergen Christoffel
2021-02-16 17:21   ` Vincent Lefevre
2021-02-16 18:29     ` Bart Schaefer
2021-02-16 21:35     ` Juergen Christoffel
2021-02-16 18:21   ` pod documentation in zsh scripts (Was: Block comments ala Ray) Stephane Chazelas

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=20210213073746.z2ruehp5jw7l55ry@chazelas.org \
    --to=stephane@chazelas.org \
    --cc=schaefer@brasslantern.com \
    --cc=vq@larryv.me \
    --cc=zsh-workers@zsh.org \
    /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).