From: Rob Browning <rlb@defaultvalue.org>
Cc: guile-devel@gnu.org, guile-user@gnu.org
Subject: Re: macros, procedure->macro
Date: Mon, 01 Jul 2002 16:30:01 -0500 [thread overview]
Message-ID: <87k7ofb0h2.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <Pine.GSO.4.05.10207012134500.15843-100000@sallust.ida.ing.tu-bs.de> (Dirk Herrmann's message of "Mon, 1 Jul 2002 21:56:23 +0200 (CEST)")
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
> That is, if we plan to split up syntax transformation,
> compilation/memoization and execution, we could not remove "acros"
> and "macros" from the execution, since they may behave differently
> every time the same code is executed.
>
> I therefore strongly suggest to get rid of "acros" and "macros". As
> a first step, I suggest to get rid of "macros" and their
> scheme-level representative procedure->macro
Presuming I'm remembering my most recent look in to this stuff
correctly (about 6 mos ago), I believe you're right, but Marius may
have further comments.
> If all results are positive, I will go ahead and remove the support
> for "macros" from guile. After that, I will take a close look at "acros"
> and we will play a similar game with "acros" again...
It may also be important to consider pssyntax (i.e. syntax-case,
etc.). In the end I'd like to have one unified macro system whose
behavior and interactions with the rest of guile are very clear.
Thanks
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG=1C58 8B2C FB5E 3F64 EA5C 64AE 78FE E5FE F0CB A0AD
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-07-01 21:30 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-01 19:56 macros, procedure->macro Dirk Herrmann
2002-07-01 21:30 ` Rob Browning [this message]
2002-07-03 20:24 ` Dirk Herrmann
2002-07-01 22:14 ` Marius Vollmer
2002-07-03 20:11 ` Dirk Herrmann
2002-07-07 17:54 ` Marius Vollmer
2002-07-08 20:31 ` Dirk Herrmann
2002-07-09 18:22 ` Marius Vollmer
2002-07-10 5:21 ` Dirk Herrmann
2002-07-10 19:31 ` Marius Vollmer
2002-07-10 19:57 ` Dirk Herrmann
2002-07-10 20:08 ` Marius Vollmer
2002-07-01 22:17 ` Gary Houston
2002-07-09 21:16 ` Neil Jerram
2002-07-10 5:46 ` Dirk Herrmann
2002-07-10 10:15 ` Neil Jerram
2002-07-10 20:03 ` Dirk Herrmann
2002-07-13 0:09 ` Neil Jerram
2002-07-13 2:36 ` Clinton Ebadi
2002-07-14 15:23 ` Neil Jerram
2002-07-14 16:26 ` Marius Vollmer
2002-07-15 6:03 ` Rob Browning
2002-07-13 6:53 ` Dirk Herrmann
2002-07-14 15:23 ` Neil Jerram
[not found] <200207012220.PAA08054@onyx.he.net>
2002-07-03 20:08 ` Dirk Herrmann
2002-07-04 20:16 ` Dirk Herrmann
2002-07-07 18:15 ` Marius Vollmer
[not found] <87n0t376c9.fsf@zagadka.ping.de>
2002-07-08 20:23 ` Dirk Herrmann
2002-07-09 18:13 ` Marius Vollmer
2002-07-10 21:54 ` Dirk Herrmann
2002-07-13 9:53 ` Dirk Herrmann
2002-07-13 18:38 ` Marius Vollmer
[not found] <m3lm8e5o69.fsf@laruns.ossau.uklinux.net>
2002-07-14 21:35 ` Dirk Herrmann
2002-07-15 20:48 ` Marius Vollmer
2002-07-15 22:42 ` Neil Jerram
2002-07-16 22:00 ` Dirk Herrmann
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=87k7ofb0h2.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
--cc=guile-devel@gnu.org \
--cc=guile-user@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).