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:33:43 -0800 (PST) [thread overview]
Message-ID: <200311110433.UAA23193@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: Tom Lord <lord@emf.net>
> Guile currently does not detect that error and simply returns 6 for
> the second, error-laden, form. Thus, Guile's conformance is saved in
> this instance by the distinction between "is an error" and "an error
> is signaled".
> It is _slightly_ intimidating to think of what would be required of an
> implementation, especially an SCM-derived implementation, to actually
> detect that error. Overall, Guile suffers from the sin of SCM -- of
> not making expansion and evaluation separate phases.
I just wanted to add that the SCM-family's approach to macros _is_
intrinsicly useful -- as a kind of primitive for implementing
graph-rewriting systems -- even though it's not (without extreme
contortions) appropriate for Scheme macros.
It might be fun to see if someone can make a useful normal-order
evaluation functional langauge using SCM's defmacro facility....
-t
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2003-11-11 4:33 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
2003-11-11 4:33 ` Tom Lord [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=200311110433.UAA23193@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).