unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Kevin Ryde <user42@zip.com.au>
Subject: Re: make-shared-substring
Date: Thu, 09 Oct 2003 09:52:47 +1000	[thread overview]
Message-ID: <87n0cbmgmo.fsf@zip.com.au> (raw)
In-Reply-To: <8765j17wtg.fsf@zagadka.ping.de> (Marius Vollmer's message of "Tue, 07 Oct 2003 19:59:55 +0200")

Marius Vollmer <mvo@zagadka.de> writes:
>
> Providing it in 1.7 is too much hassle, I'd say, since it would
> need to whole shared string mechanism.

Oh, to make it genuinely shared.  Yep.  I guess guile-www is only
using it as an optimization, not because a change in one string should
appear in another.


_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel


      reply	other threads:[~2003-10-08 23:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-03 23:29 make-shared-substring Kevin Ryde
2003-10-04  2:58 ` make-shared-substring Clinton Ebadi
2004-01-08 22:09   ` make-shared-substring Kevin Ryde
2003-10-07 17:59 ` make-shared-substring Marius Vollmer
2003-10-08 23:52   ` Kevin Ryde [this message]

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=87n0cbmgmo.fsf@zip.com.au \
    --to=user42@zip.com.au \
    /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).