unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Zelphir Kaltstahl <zelphirkaltstahl@posteo.de>
To: Matt Wette <matt.wette@gmail.com>, Guile User <guile-user@gnu.org>
Subject: Re: syntax taste: use of unquote in macros
Date: Mon, 30 Mar 2020 00:07:07 +0200	[thread overview]
Message-ID: <91a7553d-2f04-4319-3437-fbe05cddde47@posteo.de> (raw)
In-Reply-To: <dd403a66-123b-2855-39cb-7b5c5f36cd9a@gmail.com>


On 3/29/20 5:11 PM, Matt Wette wrote:
> Hi All,
>
> I'm not sure if you know about this, but there is a discrepancy in the
> way some folks define macros to use unquote (aka ,).   For example,
>
> > (use-modules (system base pmatch))
> > (pmatch '(foo "bar")  ((foo ,val)  (write val) (newline)))
> => "bar"
>
> > (use-modules (ice-9 match))
> > (match '(foo "bar")  (`(foo ,val)  (write val) (newline)))
> => "bar"
>
> Note the difference in the use of quasiquote (aka `) in the pattern
> for (foo ,val): match syntax uses it, pmatch does not.
> In Scheme, quasiquote and unquote always come together.
>
> Is pmatch syntax in bad taste?  I'm looking for opinions.
>
> Another example is sxml-match, which omits use of quasiquote.
> I have written a variation of sxml-match.  Should I keep the sxml-match
> usage, which keeps it compatible with sxml-match,  or adopt that
> used by (ice-9 match)?
>
> Matt

Hi Matt!

I'm not sure where I first read about pmatch doing the quasiquote
internally automatically and I of course had already forgotten about it,
until I read your e-mail. I remember though: When I read about it, I
thought something like: "Ehhh? That's confusing. Everywhere else you
have to quasiquote to unquote, but in pmatch it's different. Easy to
forget that and I need to remember more. I would not mind having to
write a simple quasiquote myself."

So, with my limited experience, I would definitely vote for the, in my
opinion more natural way, to have the user write the quasiquote, instead
of doing that internally. It's not saving that much time or writing
really. I understand the idea, that "if it is always done anyway, one
could save the user some typing of the same thing over and over again",
but in my opinion it is not worth it to deviate from, what one would
expect without knowing about this behavior.

Regards,
Zelphir




  reply	other threads:[~2020-03-29 22:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-29 15:11 syntax taste: use of unquote in macros Matt Wette
2020-03-29 22:07 ` Zelphir Kaltstahl [this message]
2020-03-30 10:34   ` tomas
2020-03-30 23:43     ` Matt Wette
2020-03-31  9:19       ` tomas
2020-03-30 13:07 ` Arne Babenhauserheide
2020-03-31 16:56 ` Ludovic Courtès

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.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=91a7553d-2f04-4319-3437-fbe05cddde47@posteo.de \
    --to=zelphirkaltstahl@posteo.de \
    --cc=guile-user@gnu.org \
    --cc=matt.wette@gmail.com \
    /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).