From: prj@po.cwru.edu (Paul Jarc)
Cc: guile-user@gnu.org, Roland Orre <orre@nada.kth.se>
Subject: Re: shared-substrings missing in 1.7
Date: Fri, 16 Jan 2004 15:24:18 -0500 [thread overview]
Message-ID: <m3wu7rprp3.fsf@multivac.cwru.edu> (raw)
In-Reply-To: <rmillo7u2pv.fsf@fnord.ir.bbn.com>
Greg Troxel <gdt@ir.bbn.com> wrote:
> This is a guile-specific non-R5RS feature, AFAICT. It seems a bit
> non-Schemely, too, for a mutation of one object to cause another to
> change
Implicit copy-on-write substrings would be nice, though. Not that I'm
volunteering. :)
> As I've used shared substrings it is also non trivial to
> change the code.
>
> So it sounds like you have code that depends on the cross-mutability
> behavior.
No, I think his code simply runs extremely slowly without shared
substrings.
paul
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2004-01-16 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 8:49 shared-substrings missing in 1.7 Roland Orre
2004-01-16 12:52 ` Marco Parrone
2004-01-16 13:49 ` Roland Orre
2004-01-16 20:29 ` Tom Lord
2004-01-16 19:13 ` Greg Troxel
2004-01-16 20:24 ` Paul Jarc [this message]
2004-01-16 20:35 ` About shared substrings Roland Orre
2004-01-16 21:12 ` Neil Jerram
2004-01-17 22:34 ` Keith Wright
2004-01-16 21:54 ` Mikael Djurfeldt
2004-01-16 22:00 ` Tom Lord
2004-01-16 20:45 ` shared-substrings missing in 1.7 Tom Lord
2004-01-19 16:54 ` Greg Troxel
2004-01-20 9:02 ` tomas
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=m3wu7rprp3.fsf@multivac.cwru.edu \
--to=prj@po.cwru.edu \
--cc=guile-user@gnu.org \
--cc=orre@nada.kth.se \
/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).