From: Marius Vollmer <mvo@zagadka.ping.de>
Cc: guile-devel@gnu.org
Subject: Re: bug in syncase
Date: 16 Nov 2002 19:39:24 +0100 [thread overview]
Message-ID: <87u1ihs6jn.fsf@zagadka.ping.de> (raw)
In-Reply-To: <Pine.GSO.4.05.10211141245330.4453-100000@sallust.ida.ing.tu-bs.de>
Dirk Herrmann <dirk@sallust.ida.ing.tu-bs.de> writes:
> the separation of memoization and execution is going forward.
Great!
> However, in (ice-9 syncase) there is one place where I don't know how to
> fix it correctly, namely in function putprop there is the following line:
> (variable-set! v sc-macro)
> where sc-macro is a macro. As a workaround, I have changed the line to
> (variable-set! v 'sc-macro)
> but without being aware of the effects. However, the test-suite almost
> completes flawlessly now.
I can't say right now how to fix this, but in general, I think the
whole syntax transformer business needs to be redone for a separate
memoizer/compiler pass. That is, it is OK when your new evaluator
breaks the existing syncase and this is not easily fixed. We need to
find a fix eventually, but that fix should also remove the kluginess
of the current situation completely.
In my vision, the syntax transformer in essence _is_ the memoizer.
Thus, I'd say it is acceptable that syntax-case support must be redone
from the ground up.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2002-11-16 18:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 11:59 bug in syncase Dirk Herrmann
2002-11-15 4:10 ` Clinton Ebadi
2002-11-15 9:29 ` Lynn Winebarger
2002-11-15 9:34 ` Lynn Winebarger
2002-11-15 19:25 ` Neil Jerram
2002-11-16 18:39 ` Marius Vollmer [this message]
2002-11-17 10:54 ` Neil Jerram
2002-11-17 20:07 ` Marius Vollmer
[not found] <Pine.GSO.4.05.10211161811180.9959-100000@sallust.ida.ing.tu-bs.de>
2002-11-17 12:11 ` Neil Jerram
2002-11-20 17:33 ` Dirk Herrmann
2002-11-21 17:53 ` Dirk Herrmann
2002-11-21 20:22 ` Neil Jerram
2002-11-23 10:53 ` Dirk Herrmann
2002-11-24 9:25 ` Neil Jerram
2002-11-24 10:33 ` Dirk Herrmann
2002-12-04 1:12 ` Rob Browning
2002-11-23 13:01 ` Marius Vollmer
2002-12-04 18:27 ` Carl R. Witty
2002-12-04 20:54 ` Neil Jerram
2002-12-09 20:28 ` Carl R. Witty
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=87u1ihs6jn.fsf@zagadka.ping.de \
--to=mvo@zagadka.ping.de \
--cc=guile-devel@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).