From: "Harrison, John R" <john.r.harrison@intel.com>
To: "Martin Jambon" <martin.jambon@ens-lyon.org>
Cc: "OCaml" <caml-list@inria.fr>,
"David Teller" <David.Teller@univ-orleans.fr>
Subject: RE: [Caml-list] Read-only arrays ?
Date: Tue, 10 Apr 2007 14:57:31 -0700 [thread overview]
Message-ID: <509223F0BF55E74FA1247D17207E7A0C014E5043@orsmsx419.amr.corp.intel.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0704101427500.21749@localhost>
| This topic comes up from time to time... My take on this is that
read-only
| arrays or strings are not badly needed.
Of course, this is a matter of opinion. In the end you didn't offer
a solution to the specific problem I had. I'll still need to adopt
an expensive and/or ugly workaround if I really want to protect myself
against OCaml's mutable strings. However, I accept that my application
is not typical.
John.
next prev parent reply other threads:[~2007-04-10 21:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-10 21:03 David Teller
2007-04-10 21:35 ` [Caml-list] " Martin Jambon
2007-04-10 21:57 ` Harrison, John R [this message]
2007-04-10 23:12 ` Martin Jambon
2007-04-11 5:08 ` David Teller
2007-04-11 5:31 ` Jacques Garrigue
2007-04-11 5:50 ` Jon Harrop
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=509223F0BF55E74FA1247D17207E7A0C014E5043@orsmsx419.amr.corp.intel.com \
--to=john.r.harrison@intel.com \
--cc=David.Teller@univ-orleans.fr \
--cc=caml-list@inria.fr \
--cc=martin.jambon@ens-lyon.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 NNTP newsgroup(s).