From: Alain Frisch <Alain.Frisch@inria.fr>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Not really a bug but...
Date: Sat, 16 Jun 2007 09:30:16 +0200 [thread overview]
Message-ID: <46739188.5060605@inria.fr> (raw)
In-Reply-To: <200706160117.45971.jon@ffconsultancy.com>
Jon Harrop wrote:
> Any chance of changing the semantics of string literals so they aren't static?
A simple Camlp4 syntax extension is enough to turn any literal "foobar"
into String.copy "foobar". (Except it doesn't work because of format
strings.) If it were done automatically, there would be a penalty for
the common case of immutable strings; to avoid it, you'd need to lift
constant literals out of abstractions, which is not very nice.
-- Alain
next prev parent reply other threads:[~2007-06-16 7:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-16 0:17 Jon Harrop
2007-06-16 7:30 ` Alain Frisch [this message]
2007-06-16 10:02 ` [Caml-list] " 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=46739188.5060605@inria.fr \
--to=alain.frisch@inria.fr \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.com \
/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).