unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
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 16:07:03 +0100	[thread overview]
Message-ID: <CAJ3okZ3F0VRhRiCO0yZJFWMr8M_po_RM=W6nB1agb=iCzuWNNA@mail.gmail.com> (raw)
In-Reply-To: <87lfpjswla.fsf@elephly.net>

Hi Ricardo,

On Mon, 3 Feb 2020 at 13:08, Ricardo Wurmus <rekado@elephly.net> wrote:

> I still think that the syntax is sub-optimal.  We support Wisp to
> make the Lispiness a little easier to swallow for the skeptics.  But
> the procedure case does not benefit much from Wisp — it would look worse
> if we expressed it in the Wisp way:
>
>     process : list-file-template filename
>
> Note the space between “process” and the remainder.  It would be wrong
> to remove the space after “process”.  That’s a pitfall stemming from a
> familiarity with YAML that I’d rather avoid.  (That’s why I want to
> rename “process:” and “workflow:”.)

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.

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) :".


> The only reason why I know how to use “:” is because I know that I want
> the remainder to be wrapped in parentheses…  People who only know the
> sugary syntax would not have that knowledge and it would just seem like
> an arbitrary thing.

Yes exactly.
To place the Wisp sugary syntax, each time I am going back to Scheme,
think where are the opening/closing parenthesis and then adapt the
sugar.


>     process list-file-template : filename

I would be tempted to write without the space.

     process list-file-template: filename


>     process list-file-template (filename)

I find this one the clearer.



All the best,
simon

  parent reply	other threads:[~2020-02-05 15:07 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 [this message]
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='CAJ3okZ3F0VRhRiCO0yZJFWMr8M_po_RM=W6nB1agb=iCzuWNNA@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).