From: Mark H Weaver <mhw@netris.org>
To: "Tommi Höynälänmaa" <tommi.hoynalanmaa@gmail.com>
Cc: guile-user@gnu.org
Subject: Re: Syntax form
Date: Wed, 23 Aug 2017 01:13:05 -0400 [thread overview]
Message-ID: <87tw0yooim.fsf@netris.org> (raw)
In-Reply-To: <f7e0ce76-1346-0417-8b96-188e6741d2bd@gmail.com> ("Tommi \=\?utf-8\?B\?SMO2eW7DpGzDpG5tYWEiJ3M\=\?\= message of "Mon, 21 Aug 2017 15:22:45 +0300")
Tommi Höynälänmaa <tommi.hoynalanmaa@gmail.com> writes:
> Where are (syntax x) forms compiled with the old vector based
> implementation of syntax objects (guile 2.0.11 or 2.2.0)? The
> structure type for the syntax objects is defined in ice-9/psyntax.scm
> but I can't find code for the syntax form.
'syntax' is a core form of the psyntax macro expander. In both 2.0 and
2.2, the code to handle expansion of 'syntax' forms is in psyntax.scm,
beginning with:
(global-extend 'core 'syntax
Although in 2.2 the text above is split between two lines:
(global-extend
'core 'syntax
Mark
prev parent reply other threads:[~2017-08-23 5:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 12:22 Syntax form Tommi Höynälänmaa
2017-08-23 5:13 ` Mark H Weaver [this message]
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=87tw0yooim.fsf@netris.org \
--to=mhw@netris.org \
--cc=guile-user@gnu.org \
--cc=tommi.hoynalanmaa@gmail.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).