From: Tom Lord <lord@emf.net>
Cc: mvo@zagadka.de, guile-devel@gnu.org, rlb@defaultvalue.org
Subject: Re: Internal defines
Date: Mon, 10 Nov 2003 20:22:51 -0800 (PST) [thread overview]
Message-ID: <200311110422.UAA23167@morrowfield.regexps.com> (raw)
In-Reply-To: <3FB05C97.9060101@cs.uvm.edu> (message from David Van Horn on Mon, 10 Nov 2003 21:50:47 -0600)
> From: David Van Horn <dvanhorn@cs.uvm.edu>
> Tom Lord wrote:
> > But I think it is crystal clear (once the subtleties understodd) that if the
> > [R5RS] denotational semantics do not support [R5RS] 5.3 then the
> > denotational semantics have a bug.
> The denotational semantics given by R5RS are for primitive expressions and
> selected built-in procedures of the language that the macro system must
> transform programs into; it makes no sense for the DS to make mention of
> macros and their errors.
> The fact that there is no formal semantics for the syntax transformation
> language is sad and would be a welcome addition to R6RS, IMO.
One way to do that is to add sufficiently to the set of primitive
expressions and built-in procedures so that macros can be explained
operationally (as a translation into those core elements carried out
by an explicit expand-phase that precedes evaluation).
If you'll forgive the self-promotion, please watch for the upcoming
Pika Scheme announcement on c.l.s. (sometime this month) which does
exactly that. In a not unrelated fashion, Pika provides a foundation
for module systems.
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-11-11 4:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 22:40 Internal defines Dirk Herrmann
2003-11-11 2:21 ` Rob Browning
2003-11-11 3:11 ` Tom Lord
2003-11-11 3:50 ` David Van Horn
2003-11-11 4:22 ` Tom Lord [this message]
2003-11-11 4:33 ` Tom Lord
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=200311110422.UAA23167@morrowfield.regexps.com \
--to=lord@emf.net \
--cc=guile-devel@gnu.org \
--cc=mvo@zagadka.de \
--cc=rlb@defaultvalue.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).