From: Arun Isaac <arunisaac@systemreboot.net>
To: Blake Shaw <blake@reproduciblemedia.com>,
David Pirotte <david@altosw.be>
Cc: Maxime Devos <maximedevos@telenet.be>, guile-devel@gnu.org
Subject: Re: [PATCH v3] docs/match: pattern matcher example makeover
Date: Fri, 03 Feb 2023 12:05:25 +0000 [thread overview]
Message-ID: <878rhfx8ca.fsf@systemreboot.net> (raw)
In-Reply-To: <7zk00zkoqc.fsf@reproduciblemedia.com>
Hi Blake,
> Well, these conventions can be found throughout the gamut of scheme
> literature going back to the 80s, and some of the largest scheme
> projects, such as Chez, Racket, etc. employ them. So if you're
> getting into Scheme, you'll necessarily encounter them, and if you
> haven't been made aware that brackets are syntactic sugar for parens
> in Scheme, or if that doesn't become apparent with some quick repl
> experimentation, you've probably jumped into pattern matching a bit
> too quickly.
>
> But overall, it seems the objections against the Indiana style here
> are primarily concerned with individual, current user/contributor
> preferences, rather than out of a concern for the target audience,
> which are newcomers.
I don't think I agree. When I was a newcomer to guile and was reading
the sxml-match documentation in the manual for the first time, I found
it very confusing that there were square brackets. At that point, I
understood match but was confounded into thinking that sxml-match was
completely different due to the square brackets. Finally, when I
understood, I contributed a patch making everything round
parentheses. https://issues.guix.gnu.org/30920
I'd say a typical newcomer is not familiar with the gamut of scheme
literature going back to the 80s. I certainly wasn't, and still am not
to be honest.
Cheers!
Arun
next prev parent reply other threads:[~2023-02-03 12:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 13:09 [PATCH v3] docs/match: pattern matcher example makeover Blake Shaw
2023-02-01 16:40 ` Maxime Devos
2023-02-02 17:47 ` David Pirotte
2023-02-03 10:05 ` Blake Shaw
2023-02-03 12:05 ` Arun Isaac [this message]
2023-02-03 13:10 ` Blake Shaw
2023-02-03 13:43 ` Josselin Poiret
2023-02-03 14:14 ` Blake Shaw
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=878rhfx8ca.fsf@systemreboot.net \
--to=arunisaac@systemreboot.net \
--cc=blake@reproduciblemedia.com \
--cc=david@altosw.be \
--cc=guile-devel@gnu.org \
--cc=maximedevos@telenet.be \
/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).