From: Matt Wette <matt.wette@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: problems with syntax-case and with-syntax
Date: Sun, 27 Aug 2017 20:50:12 -0700 [thread overview]
Message-ID: <AC42E163-67A4-468B-8F98-1A4B4CDB08D1@gmail.com> (raw)
In-Reply-To: <87lgm4il3u.fsf@netris.org>
> On Aug 27, 2017, at 5:36 PM, Mark H Weaver <mhw@netris.org> wrote:
>
> FWIW, I've always been opposed to these non-standard semantics, but they
> were included in Guile 2.2 over my strenuous objections:
>
> https://lists.gnu.org/archive/html/guile-devel/2014-01/msg00061.html
> https://lists.gnu.org/archive/html/guile-devel/2011-11/msg00021.html
> https://lists.gnu.org/archive/html/guile-devel/2011-11/msg00042.html <https://lists.gnu.org/archive/html/guile-devel/2011-11/msg00042.html>
I look forward to reading through this thread.
Matt
next prev parent reply other threads:[~2017-08-28 3:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-27 20:18 problems with syntax-case and with-syntax Matt Wette
2017-08-28 0:36 ` Mark H Weaver
2017-08-28 1:35 ` Mark H Weaver
2017-09-18 13:16 ` Matt Wette
2017-09-20 12:50 ` Matt Wette
2017-08-28 3:48 ` Matt Wette
2017-08-28 3:50 ` Matt Wette [this message]
2017-08-28 11:38 ` Chris Vine
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=AC42E163-67A4-468B-8F98-1A4B4CDB08D1@gmail.com \
--to=matt.wette@gmail.com \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
/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).