From: Kevin Ryde <user42@zip.com.au>
Cc: hanwen@cs.uu.nl
Subject: Re: core dump.
Date: Fri, 23 Jan 2004 08:45:29 +1000 [thread overview]
Message-ID: <87isj338mu.fsf@zip.com.au> (raw)
In-Reply-To: <16399.49843.477766.969664@localhost.localdomain> (Han-Wen Nienhuys's message of "Thu, 22 Jan 2004 13:31:47 +0100")
Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
>
> Does anyone actually know how the evaluator works?
For what it's worth, a small example I struck tickling the (or a)
problem in this area is
(define my-macro
(procedure->memoizing-macro
(lambda (expr env)
(list 'let expr))))
(my-macro 1 2 3)
The let generated is obviously wrong. I suspected the memoizing or
something creates a circular list, or something, which has trouble
printing or unmemoizing, or something.
I think it should be pretty important to get even the worst and most
obvious flaws printing successfully under --debug, since of course one
is using that option because it's apparently not obvious what's wrong
:-).
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2004-01-22 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <16397.52459.731364.359708@localhost.localdomain>
[not found] ` <87k73lug4x.fsf@zip.com.au>
2004-01-22 12:31 ` core dump Han-Wen Nienhuys
2004-01-22 16:20 ` Dirk Herrmann
2004-01-22 22:45 ` Kevin Ryde [this message]
2004-01-23 17:40 ` Neil Jerram
[not found] ` <1075297977.5072.37.camel@localhost>
2004-02-06 20:19 ` uniform-vector? gives true for list Roland Orre
2004-02-14 0:07 ` Kevin Ryde
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=87isj338mu.fsf@zip.com.au \
--to=user42@zip.com.au \
--cc=hanwen@cs.uu.nl \
/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).