From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: Lynn Winebarger <owinebar@free-expression.org>,
Guile Development List <guile-devel@gnu.org>
Subject: Re: Syntax checks
Date: 14 Apr 2002 20:11:25 +0200 [thread overview]
Message-ID: <871ydip2uq.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.LNX.4.21.0204131032500.22358-100000@marvin.ida.ing.tu-bs.de>
Dirk Herrmann <dirk@ida.ing.tu-bs.de> writes:
> IMO, the current solution is broken.
Yes, my opinion as well.
> Thus, I sugggest to first go the way that Lynn suggests: Do
> expansion after reading, but don't care about re-compilation. If we
> later decide for re-compilation, we can think about possible
> solutions then.
Yes. More detailed:
- revoke macro transformers from being stored in variables. I.e.
(define-macro (foo ...) ...)
(define bar foo)
will no longer work. Instead, put macros into the toplevel by
binding them directly to a symbol. We now have
(module lookup) (variable-ref)
symbol ------> variable ------> #<macro>
but should have
(module lookup)
symbol ------> #<macro>
- Make syntax-case use this arrangement, and make it work correctly
with modules in general.
- Separate memoization from execution.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-04-14 18:11 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-06 6:25 Syntax checks Dirk Herrmann
2002-04-06 15:38 ` Neil Jerram
2002-04-07 7:09 ` Dirk Herrmann
2002-04-08 18:27 ` Neil Jerram
2002-04-07 10:40 ` Marius Vollmer
2002-04-09 20:48 ` Lynn Winebarger
2002-04-13 9:01 ` Dirk Herrmann
2002-04-13 12:48 ` Neil Jerram
2002-04-13 18:28 ` Lynn Winebarger
2002-04-13 18:10 ` Lynn Winebarger
2002-04-14 18:18 ` Marius Vollmer
2002-04-14 18:11 ` Marius Vollmer [this message]
2002-04-23 21:55 ` Thien-Thi Nguyen
2002-04-14 17:52 ` Marius Vollmer
2002-04-29 23:55 ` Lynn Winebarger
2002-05-07 19:24 ` Marius Vollmer
2002-05-09 5:59 ` Lynn Winebarger
2002-04-07 10:05 ` Marius Vollmer
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=871ydip2uq.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@gnu.org \
--cc=owinebar@free-expression.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).