From: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
To: mhw@netris.org
Cc: guile-devel@gnu.org
Subject: Re: Feature request: Expose `ellipsis?' from psyntax.ss
Date: Wed, 21 Nov 2018 17:09:27 +0100 [thread overview]
Message-ID: <CAEYrNrRct5k0FfjLjJvOa+8-LvfOFpYPXkxswKdH2uawCOTgwg@mail.gmail.com> (raw)
In-Reply-To: <CAEYrNrRozViLCmgCyzPpqCxwJobt0oZPycf4o6wUR2h1ohCnpg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1101 bytes --]
> Now to R6RS. Section 6.4 says that auxiliary syntax describes a syntax
> binding. Section 12.4 of the R6RS Library Report defines `...' as auxiliary
> syntax. The example definition of `case' in Section 12.5 ibid. shows
> explicitely that auxiliary keywords are matched using `free-identifier=?'
> (in this example, `else'). Also, in all other regards with respect to
> auxiliary syntax R6RS does not differ from R7RS.
>
P.S.: I just noticed that Guile does not export `...' from (rnrs base),
which is an incompatiblity to the R6RS that is not mentioned by the
following list, I think:
https://www.gnu.org/software/guile/manual/html_node/R6RS-Incompatibilities.html#R6RS-Incompatibilities.
Likewise, identifiers like `else' and `=>' are not exported by the Guile
version of `(rnrs base)'. Oddly enough, other auxiliary syntax like
`unquote' is being bound.
It is probably enough to create the missing bindings around these lines in
psyntax.scm:
http://git.savannah.gnu.org/cgit/guile.git/tree/module/ice-9/psyntax.scm#n3230
and to export the bindings from `(guile)', `(rnrs base)', `(rnrs)', etc.
[-- Attachment #2: Type: text/html, Size: 1826 bytes --]
next prev parent reply other threads:[~2018-11-21 16:09 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:16 Feature request: Expose `ellipsis?' from psyntax.ss Marc Nieper-Wißkirchen
2018-11-14 19:10 ` Mark H Weaver
2018-11-14 20:27 ` Marc Nieper-Wißkirchen
2018-11-15 9:38 ` Mark H Weaver
2018-11-15 10:03 ` Marc Nieper-Wißkirchen
2018-11-15 10:59 ` Mark H Weaver
2018-11-15 19:41 ` Marc Nieper-Wißkirchen
2018-11-16 0:00 ` Mark H Weaver
2018-11-16 13:37 ` Marc Nieper-Wißkirchen
2018-11-16 23:36 ` Mark H Weaver
2018-11-17 15:03 ` Marc Nieper-Wißkirchen
2018-11-21 3:37 ` Mark H Weaver
2018-11-21 8:40 ` Marc Nieper-Wißkirchen
2018-11-21 16:09 ` Marc Nieper-Wißkirchen [this message]
2018-11-23 7:55 ` Mark H Weaver
2018-11-23 21:06 ` Marc Nieper-Wißkirchen
2018-11-23 20:25 ` Mark H Weaver
2018-11-23 21:28 ` Marc Nieper-Wißkirchen
2018-11-24 9:08 ` Marc Nieper-Wißkirchen
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=CAEYrNrRct5k0FfjLjJvOa+8-LvfOFpYPXkxswKdH2uawCOTgwg@mail.gmail.com \
--to=marc@nieper-wisskirchen.de \
--cc=guile-devel@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).