From: "Frank A. Christoph" <christo@nextsolution.co.jp>
To: "Claudio Sacerdoti Coen" <sacerdot@students.cs.unibo.it>,
<caml-list@inria.fr>
Subject: RE: symbol managment in Caml
Date: Sat, 26 Feb 2000 15:13:25 +0900 [thread overview]
Message-ID: <000101bf8020$973365a0$0150ebca@nextsolution.co.jp> (raw)
In-Reply-To: <20000225181006.A18284@students.cs.unibo.it>
[re: hashing identifiers]
> I have had the same problem and I was about to write the
> new function when I stopped: the time taken by the hash
> function was not worth the extra coding.
Even if it takes more, or as much, time as comparing identifiers directly,
there is still an advantage to interning strings: you can share their
representations. Of course, if you don't expect much sharing, or you don't
expect to allocate many identifiers during any single run, it may still not
be worht it.
--fac
next prev parent reply other threads:[~2000-02-28 23:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-25 12:16 Stephan Houben
2000-02-25 16:21 ` skaller
2000-02-25 16:25 ` Judicael Courant
2000-02-25 17:10 ` Claudio Sacerdoti Coen
2000-02-26 6:13 ` Frank A. Christoph [this message]
2000-02-28 9:49 ` Sven LUTHER
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='000101bf8020$973365a0$0150ebca@nextsolution.co.jp' \
--to=christo@nextsolution.co.jp \
--cc=caml-list@inria.fr \
--cc=sacerdot@students.cs.unibo.it \
/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