From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: Commercial development
Date: Sun, 05 Jun 2005 23:41:22 +0300 [thread overview]
Message-ID: <87zmu4k03x.fsf@zagadka.de> (raw)
In-Reply-To: <4266AC41.4050105@ossau.uklinux.net> (Neil Jerram's message of "Wed, 20 Apr 2005 20:23:45 +0100")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Is this a good fix for r5rs_pitfall 1.1?
scm_copy_tree is too much, since it makes the following code fail:
(let ((a '(1 2 3))) (letrec ((x a) (y a)) (eq? x y)))
We should not copy the values themselves, just the storage cells;
thus, scm_list_copy is the right thing here.
But should we make that change? I am not sure. It causes some
significant run-time overhead for an obscure benefit. For now I'll
just put in some comments in eval.c and r5rs_pitfall.test.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-06-05 20:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d3llfr$u1k$1@nnrp.waia.asn.au>
[not found] ` <115t7ajdbfq8348@corp.supernews.com>
[not found] ` <871x966hwn.fsf@naia.workingwithlinux.com>
[not found] ` <426505c8$0$196$edfadb0f@dread12.news.tele.dk>
[not found] ` <Pine.LNX.4.58-L.0504191954120.15565@klodrik.uio.no>
[not found] ` <iM-dnUKnNq7zyPjfRVn-gw@giganews.com>
[not found] ` <426601FF.6010600@ossau.uklinux.net>
[not found] ` <9qGdnYkVut1t0PvfRVn-rw@giganews.com>
2005-04-20 19:19 ` Commercial development Neil Jerram
2005-04-20 19:23 ` Neil Jerram
2005-06-05 20:41 ` Marius Vollmer [this message]
2005-06-07 22:04 ` Neil Jerram
2005-06-08 19:03 ` Neil Jerram
2005-06-11 20:56 ` Marius Vollmer
2005-06-12 7:30 ` Neil Jerram
2005-06-12 9:38 ` Neil Jerram
2005-07-18 20:53 ` Neil Jerram
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=87zmu4k03x.fsf@zagadka.de \
--to=mvo@zagadka.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).