From: Richard Jones <rich@annexia.org>
To: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
Cc: OCaml List <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Strings
Date: Sun, 5 Apr 2009 21:54:57 +0100 [thread overview]
Message-ID: <20090405205457.GA22985@annexia.org> (raw)
In-Reply-To: <8697F924-0485-4E00-81DF-9BCF74D872EA@erratique.ch>
On Fri, Apr 03, 2009 at 07:50:48PM +0200, Daniel Bünzli wrote:
> Having immutable strings would not rely on the client for correctness
> of operation and that's always an advantage. Of course you'll tell me
> just use String.copy inside xmlm et voilà, but then you traded
> correctness for performance in a case where you could have both with
> immutable strings.
Could you not just define a new module which is String, but with a
restricted interface (removing all the functions that can modify
strings)? This is essentially what Batteries does, along with a bit
of camlp4 [I think] to provide a rope construction syntax.
Rich.
--
Richard Jones
Red Hat
next prev parent reply other threads:[~2009-04-05 20:54 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 11:56 Strings Jon Harrop
2009-04-03 12:25 ` [Caml-list] Strings Paolo Donadeo
2009-04-03 14:18 ` Ashish Agarwal
2009-04-03 14:46 ` Jon Harrop
2009-04-03 15:03 ` Daniel Bünzli
2009-04-03 16:52 ` Martin Jambon
2009-04-03 17:50 ` Daniel Bünzli
2009-04-03 19:46 ` Paolo Donadeo
2009-04-03 20:41 ` Harrison, John R
2009-04-04 10:11 ` Jon Harrop
2009-04-04 11:12 ` David Teller
2009-04-04 11:40 ` Jon Harrop
2009-04-04 12:34 ` David Rajchenbach-Teller
2009-04-18 12:31 ` Arkady Andrukonis
2009-04-04 10:13 ` Jon Harrop
2009-04-03 21:44 ` Goswin von Brederlow
2009-04-04 9:10 ` David Rajchenbach-Teller
2009-04-05 10:06 ` Strings Zheng Li
2009-04-06 9:20 ` Strings David Rajchenbach-Teller
2009-04-06 10:07 ` Strings Goswin von Brederlow
2009-04-06 11:03 ` Strings Zheng Li
2009-04-04 17:11 ` [Caml-list] Strings Kuba Ober
2009-04-04 17:26 ` Jon Harrop
2009-04-05 20:54 ` Richard Jones [this message]
2009-04-05 23:40 ` Daniel Bünzli
2009-04-03 18:24 ` Florian Hars
2009-04-03 20:34 ` Arnaud Spiwack
2009-04-04 10:20 ` Jon Harrop
2009-04-04 9:14 ` David Rajchenbach-Teller
2009-04-04 9:26 ` Alp Mestan
2009-04-04 10:55 ` blue storm
2009-04-04 21:51 ` Goswin von Brederlow
2009-04-04 23:35 ` Yaron Minsky
2009-04-05 9:36 ` David Rajchenbach-Teller
2009-04-05 10:08 ` Alp Mestan
2009-04-05 21:41 ` Goswin von Brederlow
2009-04-05 21:40 ` Goswin von Brederlow
2009-04-05 2:55 ` Jon Harrop
2009-04-05 4:22 ` Edgar Friendly
2009-04-05 7:03 ` Goswin von Brederlow
2009-04-05 6:57 ` Goswin von Brederlow
2009-04-05 7:11 ` Jon Harrop
2009-04-04 10:11 ` Jon Harrop
2009-04-04 21:39 ` Goswin von Brederlow
2009-04-05 7:14 ` Romain Beauxis
2009-04-05 9:34 ` David Rajchenbach-Teller
2009-04-05 21:37 ` Goswin von Brederlow
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=20090405205457.GA22985@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@yquem.inria.fr \
--cc=daniel.buenzli@erratique.ch \
/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