From mboxrd@z Thu Jan 1 00:00:00 1970 References: <871rrdthmz.fsf@elephly.net> <87lfpjswla.fsf@elephly.net> <87blqcrjuz.fsf@elephly.net> From: Ricardo Wurmus Subject: Re: Comments on process template syntax In-reply-to: Date: Wed, 05 Feb 2020 22:32:53 +0100 Message-ID: <874kw4ra7u.fsf@elephly.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable To: zimoun Cc: Roel Janssen , Kyle Meyer , gwl-devel@gnu.org List-ID: zimoun writes: >> In the Python case the =E2=80=9C:=E2=80=9D 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 Yeah, I just mean that it=E2=80=99s =E2=80=9Cnoise=E2=80=9D. It doesn=E2= =80=99t represent anything (unlike the $ in Haskell). > Aside, the 'process' macro should be renamed as Kyle mentioned it. > Because it is confusing, IMHO. Yes, I=E2=80=99m considering a rename, but I=E2=80=99m not sure which is th= e best option. We could either have (1) =E2=80=9Cdefine-process=E2=80=9D (for val= ue + definition) and =E2=80=9Cprocess=E2=80=9D (for just the value), or we could= have (2) =E2=80=9Cprocess=E2=80=9D (for value + definition) and =E2=80=9Cmake-proces= s=E2=80=9D (for just the value). I=E2=80=99m torn on this because option 1 seems correct, but option 2 resul= ts in less boilerplate as users need to bind processes to variables in order to reference them in a workflow definition. I=E2=80=99ll likely go with option 2. We only need to decide whether the =E2=80=9Cprocess=E2=80=9D macro (for val= ue + definition) should also be available by default in Scheme workflows or if it should only be enabled by default in Wisp workflows. -- Ricardo