From: "Marc Nieper-Wißkirchen" <marc@nieper-wisskirchen.de>
To: guile-devel@gnu.org
Subject: Feature request: Expose `ellipsis?' from psyntax.ss
Date: Wed, 14 Nov 2018 14:16:22 +0100 [thread overview]
Message-ID: <CAEYrNrTAeg_u3KAAo20PpKpgbjRR2xiVemCX4gTmm68ZVZeBBg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 610 bytes --]
Guile includes a mechanism to specify a custom ellipsis for `syntax-case'
macros. For macro writers it would be nice if there were a way to check
whether a given identifier is the current (custom) ellipsis.
The `ellipsis?' procedure in psyntax.ss does exactly this, but it isn't
available to user code. Re-implementing it is not possible without
accessing internal details like the special identifier #{ $sc-ellipsis }#
and without resorting to hacks.
Thus, I would like to ask to add `ellipsis?' to the list of procedures
exported by Guile (like `identifier?` or `bound-identifier=?` already are).
-- Marc
[-- Attachment #2: Type: text/html, Size: 724 bytes --]
next reply other threads:[~2018-11-14 13:16 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-14 13:16 Marc Nieper-Wißkirchen [this message]
2018-11-14 19:10 ` Feature request: Expose `ellipsis?' from psyntax.ss 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
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=CAEYrNrTAeg_u3KAAo20PpKpgbjRR2xiVemCX4gTmm68ZVZeBBg@mail.gmail.com \
--to=marc@nieper-wisskirchen.de \
--cc=guile-devel@gnu.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).