From: Kyle Meyer <kyle@kyleam.com>
To: Ricardo Wurmus <rekado@elephly.net>, Roel Janssen <roel@gnu.org>
Cc: gwl-devel@gnu.org
Subject: Re: Comments on process template syntax
Date: Wed, 05 Feb 2020 02:12:56 +0000 [thread overview]
Message-ID: <87zhdx3hp3.fsf@kyleam.com> (raw)
In-Reply-To: <874kw6slwm.fsf@elephly.net>
Ricardo Wurmus <rekado@elephly.net> writes:
> I just realized that this is not easily accomplished without warts. The
> reason is that we have no way of distinguishing this
> [...]
> Or what about this:
>
> (process list-file-template
> (name some-variable-name)
> (inputs …)
> (outputs …))
>
> Is this a process template with two arguments “name” and
> “some-variable-name”, or is this a process with a name field whose value
> is whatever “some-variable-name” evaluates to? The power of macros only
> gets us that far. Sure we could add even more heuristics and check
> whether things in the first position are identifiers and such, but this
> sounds terribly complex.
>
> This can all be avoided with a tad more syntax, but it’s slightly less
> elegant:
>
> process list-file-template (with filename)
> name …
> inputs …
> outputs …
>
> [...]
>
> Thoughts?
I agree that using an identifier seems like the best solution. I
suppose there's also the question of which word to use. "with" seems
like a good choice to me.
next prev parent reply other threads:[~2020-02-05 2:12 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 [this message]
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
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=87zhdx3hp3.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=roel@gnu.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.
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).