From: Nicolas George <nicolas.george@ens.fr>
To: caml-list@inria.fr
Subject: Re: [Caml-list] Non-mutable strings
Date: Sun, 13 Jan 2002 21:05:33 +0100 [thread overview]
Message-ID: <20020113210533.A4461@clipper.ens.fr> (raw)
In-Reply-To: <Pine.BSF.4.40.0201101847260.2173-100000@bpr.best.vwh.net>; from bpr@bpr.best.vwh.net on Fri, Jan 11, 2002 at 09:50:43AM +0000
Le duodi 22 nivôse, an CCX, Brian Rogoff a écrit :
> Sure, that works, but I think if the Caml community really wants immutable
> strings (and it seems that quite a few people do) it might make sense to
> try some alternative implementations, like ropes. It was mentioned on
> this list that some older version of Caml used ropes; maybe they could be
> resurrected?
I second that. Something that would be really nice would be to have tail
recursive appends as efficient as with the Buffer module. And from the
syntactic viewpoint, a rule similar to the one that allow strings tokens
to be seen as format could be the solution to implement that.
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
next prev parent reply other threads:[~2002-01-13 20:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-04 2:55 [Caml-list] Stop at exception Magesh Kannan
2002-01-04 13:46 ` Xavier Leroy
2002-01-05 11:19 ` [Caml-list] Non-mutable strings Mattias Waldau
2002-01-05 22:01 ` YAMAGATA yoriyuki
2002-01-10 17:56 ` Xavier Leroy
2002-01-10 18:25 ` [Caml-list] Float and OCaml C interface Christophe Raffalli
2002-01-12 21:12 ` David Mentre
2002-01-12 21:32 ` David Mentre
2002-01-23 15:07 ` [Caml-list] " Xavier Leroy
2002-01-23 16:02 ` David Monniaux
2002-01-10 18:41 ` [Caml-list] Non-mutable strings Patrick M Doane
2002-01-10 18:50 ` Brian Rogoff
2002-01-13 20:05 ` Nicolas George [this message]
2002-01-16 19:22 ` Mattias Waldau
2002-01-17 9:56 ` YAMAGATA yoriyuki
2002-01-17 10:19 ` Jerome Vouillon
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020113210533.A4461@clipper.ens.fr \
--to=nicolas.george@ens.fr \
--cc=caml-list@inria.fr \
/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 NNTP newsgroup(s).