caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Not really a bug but...
Date: Sat, 16 Jun 2007 01:17:45 +0100	[thread overview]
Message-ID: <200706160117.45971.jon@ffconsultancy.com> (raw)


Any chance of changing the semantics of string literals so they aren't static?

# let f() = "a";;
val f : unit -> string = <fun>
# let s = f();;
val s : string = "a"
# s.[0] <- 'b';;
- : unit = ()
# f();;
- : string = "b"

-- 
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
OCaml for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists/?e


             reply	other threads:[~2007-06-16  0:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-16  0:17 Jon Harrop [this message]
2007-06-16  7:30 ` [Caml-list] " Alain Frisch
2007-06-16 10:02   ` Christophe TROESTLER
2007-06-16 10:10   ` Loup Vaillant
2007-06-16 15:59     ` Richard Jones
2007-06-16 17:01     ` skaller
2007-06-16 17:03       ` 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=200706160117.45971.jon@ffconsultancy.com \
    --to=jon@ffconsultancy.com \
    --cc=caml-list@yquem.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).