From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Comments on process template syntax
Date: Wed, 5 Feb 2020 20:14:24 +0100 [thread overview]
Message-ID: <CAJ3okZ1mb-TfRKqHuBzm7_svtqWyYfOfoxtsQEHKpXK_rryUZg@mail.gmail.com> (raw)
In-Reply-To: <87blqcrjuz.fsf@elephly.net>
Hi Ricardo
On Wed, 5 Feb 2020 at 19:04, Ricardo Wurmus <rekado@elephly.net> wrote:
> > Does it make sense to expand "process: proc arg" as "process : proc arg"?
> > Well, disallow the colon ':' in all the name (symbol) and then expand.
>
> This is not easily accomplished because “:” is a valid character in a
> symbol. So I’d have to replace the reader to disallow “:” in symbols.
> That’s a very big intervention.
Ok.
It was just an idea. :-)
> > Because this space is a drawback of Wisp, I mean at least to me.
> > Especially coming from Python where the standard is to have "def
> > proc(arg):" and not "def proc(arg) :".
>
> I see what you mean. The “:” on its own is just the Wisp way of saying
> “wrap the rest of this line in parentheses”. In Haskell that’s “$”. In
> both cases it’s separate from any identifiers.
The dollar '$' appears to me a better choice than the colon ':'.
Because the colon is used in plain English and often used elsewhere
without space (YAML, python, etc.). It is about habits.
Well, that's another story. :-)
> In the Python case the “:” serves no real purpose as far as I can tell.
Hum? The colon ':' serves as separator used by the parser, AFAIU.
I mean the colon ':' is part of the Python grammar.
https://docs.python.org/3/reference/grammar.html
Well, that's another story again. ;-)
> >> process list-file-template (filename)
> >
> > I find this one the clearer.
>
> Unfortunately, this one is not possible due to ambiguity in the process
> macro as I explained in an earlier email. We can avoid this ambiguity
> by adding “with” as extra syntax:
Sorry I unqueued my emails in order. :-)
> process list-file-template (with filename)
>
> It’s not perfect, but I don’t see another way that would be any clearer.
I am fine with the 'with' keyword.
> process list-file-template with this that anything whatever
As I said elsewhere, I am not bothered by the previous syntax.
And I find equivalently nice the both using 'with'; without or with parenthesis.
> I honestly can’t tell which of the options is better. It’s like saying
> the word “table” 50 times in a row and wondering what these odd sounds
> really mean…
:-D
Aside, the 'process' macro should be renamed as Kyle mentioned it.
Because it is confusing, IMHO.
Thank you for all these new inputs on GWL.
Cheers,
simon
next prev parent reply other threads:[~2020-02-05 19:14 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
2020-02-05 15:07 ` zimoun
2020-02-05 18:04 ` Ricardo Wurmus
2020-02-05 19:14 ` zimoun [this message]
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=CAJ3okZ1mb-TfRKqHuBzm7_svtqWyYfOfoxtsQEHKpXK_rryUZg@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--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).