From: zimoun <zimon.toutoune@gmail.com>
To: Kyle Meyer <kyle@kyleam.com>
Cc: Ricardo Wurmus <rekado@elephly.net>, gwl-devel@gnu.org
Subject: Re: Comments on process template syntax
Date: Wed, 5 Feb 2020 17:23:24 +0100 [thread overview]
Message-ID: <CAJ3okZ0i2z2KxOXR6L_z5qFyyhk7WaBC1UitJDyq=5mxWfJ7zg@mail.gmail.com> (raw)
In-Reply-To: <878slh10pf.fsf@kyleam.com>
Hi Kyle,
On Wed, 5 Feb 2020 at 17:02, Kyle Meyer <kyle@kyleam.com> wrote:
> The macro works on the Scheme representation; it doesn't influence the
> Wisp to Scheme conversion. Any of those three Wisp variants would be
> converted to the equivalent of
>
> (process list-file-template (with filename) ...)
Maybe I miss a point. :-)
Here [1] Ricardo described the goal: at the end of the process there
is something like you write.
[1] https://lists.gnu.org/archive/html/gwl-devel/2020-02/msg00016.html
The question is: what should be the "nice" syntax using the "Wisp
reader"? Do I misread something?
Maybe the confusion comes from that the same term is used for the
constructor and for the macro:
process-the-macro list-file-template (with filename)
will expand to:
(define-public list-file-template
(lambda (filename)
(process-the-constructor
...)))
I agree with you and you mentioned the confusion here [2], quoting you ;-)
<<
Perhaps. I still have the feeling that sharing the same name is risking
confusion. In particular, the fact that how 'process' should be used
depends on an import could make it harder for (1) those trying to learn
the workflow language by looking at and comparing Scheme examples from
various sources and (2) those trying to understand how Wisp maps to
Scheme.
>>
[2] https://lists.gnu.org/archive/html/gwl-devel/2020-02/msg00019.html
All the best,
simon
next prev parent reply other threads:[~2020-02-05 16:23 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 10:20 Comments on process template syntax Ricardo Wurmus
2020-02-02 23:30 ` Kyle Meyer
2020-02-03 8:08 ` Ricardo Wurmus
2020-02-03 14:22 ` Kyle Meyer
2020-02-03 15:23 ` Ricardo Wurmus
2020-02-03 23:16 ` Kyle Meyer
2020-02-04 9:55 ` Ricardo Wurmus
2020-02-05 1:48 ` Kyle Meyer
2020-02-05 15:14 ` zimoun
2020-02-03 8:58 ` Roel Janssen
2020-02-03 12:07 ` Ricardo Wurmus
2020-02-03 12:56 ` Roel Janssen
2020-02-03 14:33 ` Ricardo Wurmus
2020-02-04 10:10 ` Ricardo Wurmus
2020-02-05 2:12 ` Kyle Meyer
2020-02-05 15:21 ` zimoun
2020-02-05 15:29 ` Kyle Meyer
2020-02-05 15:37 ` zimoun
2020-02-05 16:02 ` Kyle Meyer
2020-02-05 16:23 ` zimoun [this message]
2020-02-05 15:07 ` zimoun
2020-02-05 18:04 ` Ricardo Wurmus
2020-02-05 19:14 ` zimoun
2020-02-05 21:32 ` Ricardo Wurmus
2020-02-06 11:59 ` zimoun
2020-02-05 14:56 ` zimoun
2020-02-08 12:34 ` Ricardo Wurmus
2020-02-05 14:50 ` zimoun
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
List information: https://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ0i2z2KxOXR6L_z5qFyyhk7WaBC1UitJDyq=5mxWfJ7zg@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=rekado@elephly.net \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).