From: Duncan Mak <duncanmak@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa mailing list <kawa@sourceware.org>
Subject: Re: questions on libraries, pattern matching etc
Date: Mon, 29 Jun 2020 16:50:26 -0400 [thread overview]
Message-ID: <CABgWrqrcRmBtuBf52_-PgFLwpiYUwVTptHjREknY7FRLC5mGXQ@mail.gmail.com> (raw)
In-Reply-To: <c68b192b-b967-ba77-6b50-362bcf5f6b6e@bothner.com>
Hello Per,
About the syntax for a match macro, work on SRFI 200 (draft) just started:
https://srfi.schemers.org/srfi-200/srfi-200.html
What do you think about adopting the syntax for the Wright-Cartwright-Shinn
matcher?
I've been trying to use match.scm (and its variants) in Kawa and simple
patterns kinda work, but I see that:
- matching records
- matching quasiquotes
These two parts don't seem to be working.
For now, I've backed out of using match.scm due to the missing features,
but it'd really be nice to have a match macro that comes with Kawa scheme,
following one of the grammar listed in the SRFI.
Going a different direction, this design for a CASE* macro is also
interesting,
https://github.com/axch/pattern-case/blob/master/pattern-matching.txt
Duncan.
On Sun, Dec 15, 2019 at 7:59 PM Per Bothner <per@bothner.com> wrote:
> On 12/15/19 3:46 PM, Ben wrote:
> > hi
> > I'd like to test how I can use pattern match in Kawa. First I did try to
> use Kawas pattern matching function, but from what I saw it is a bit
> limited, for example there is no matching of lists.
>
> Actually, there is matching of lists, but by matching them as general
> sequences:
>
> #|kawa:1|# (! [a b c @rest] [1 2 3 4 5 6])
> #|kawa:2|# (format "a: ~a b: ~a c: ~a rest: ~a~%" a b c rest)
> a: 1 b: 2 c: 3 rest: #(4 5 6)
>
> Implementing more general matching is mainly an issue of design including
> deciding on a syntax.
> Fundamentally, should be syntax for matching a pair be:
>
> (! (pat_car . pat_cdr) value)
>
> or:
>
> (! (cons pat_car pat_cdr) value)
>
> or something else?
> The latter is used in Racket, and is more flexible, I believe, but not as
> elegant -
> which ties back to fundamental awkwardness with the Scheme evaluation
> model.
>
> Of course once we/I decide on a syntax, then it needs to be implemented,
> but
> should be fairly straight-forward, given the existing framework.
> --
> --Per Bothner
> per@bothner.com http://per.bothner.com/
>
--
Duncan.
next prev parent reply other threads:[~2020-06-29 20:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 23:47 Ben
2019-12-16 0:59 ` Per Bothner
2020-02-19 21:39 ` Duncan Mak
2020-02-20 11:00 ` Kjetil Matheussen
2020-06-29 20:50 ` Duncan Mak [this message]
2020-06-29 21:49 ` Per Bothner
2020-06-30 4:38 ` Duncan Mak
2020-06-30 5:48 ` Per Bothner
2020-07-01 4:52 ` Per Bothner
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CABgWrqrcRmBtuBf52_-PgFLwpiYUwVTptHjREknY7FRLC5mGXQ@mail.gmail.com \
--to=duncanmak@gmail.com \
--cc=kawa@sourceware.org \
--cc=per@bothner.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).