From: "Daniel Bünzli" <daniel.buenzli@erratique.ch>
To: Kihong Heo <khheo@ropas.snu.ac.kr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] variable sharing
Date: Mon, 7 Mar 2011 11:19:19 +0100 [thread overview]
Message-ID: <AANLkTikXE9DoZFsKirdwnZN=S54Tbs+yY=XdP28Qixti@mail.gmail.com> (raw)
In-Reply-To: <BC4F92AC-C457-4C1B-8D53-ABD38B67DEEF@ropas.snu.ac.kr>
Value sharing will not depend on the compiler but on your programing
style (and the style of the libraries you use).
When you code you should always ask yourself whether you are recycling
the values you manipulate or whether you are doing new copies of the
same data.
You may also be interested in implementing hash consing [1] for your
data structures.
Best,
Daniel
[1] http://www.lri.fr/~filliatr/ftp/publis/hash-consing.ps.gz
next prev parent reply other threads:[~2011-03-07 10:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 1:49 Kihong Heo
2011-03-07 2:07 ` Yitzhak Mandelbaum
2011-03-07 2:24 ` Kihong Heo
2011-03-07 10:19 ` Daniel Bünzli [this message]
2011-03-07 10:39 ` Julien Signoles
[not found] ` <1856328280.452099.1299464703924.JavaMail.root@zmbs4.inria.fr>
2011-03-07 10:24 ` Fabrice Le Fessant
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='AANLkTikXE9DoZFsKirdwnZN=S54Tbs+yY=XdP28Qixti@mail.gmail.com' \
--to=daniel.buenzli@erratique.ch \
--cc=caml-list@inria.fr \
--cc=khheo@ropas.snu.ac.kr \
/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).