From: Christian Lindig <lindig@cs.uni-sb.de>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Proposal for separate compilation
Date: Fri, 28 May 2004 12:14:37 +0200 [thread overview]
Message-ID: <D2D3D30E-B08F-11D8-8801-000A95DDB608@cs.uni-sb.de> (raw)
In-Reply-To: <Pine.SOL.4.44.0405281112290.9983-100000@clipper.ens.fr>
On May 28, 2004, at 11:55 AM, Alain Frisch wrote:
>
> The method used for generating of the uid for a given unit can be
> decided
> at compile time: one could compile some interfaces (like the stdlib)
> with
> a "transparent" semantics (the uid is a hash of the name, the content
> of
> the interface, and maybe a "salt" to be used as a namespace for the
> library), and some with a generative semantics.
When talking about the name of a module, I assume people so far refer to
"a", when the file is actually /some/where/lib/a.{ml,mli,cmi,cmo}.
Would it make sense to consider a configurable suffix of the file's
path instead? Say, you can tell the compiler to consider "lib/a" or
"where/lib/a" as the module's name when computing the hash. This would
be similar to a "salt". The longer the path, the more difficult it will
become to move files around; hence it is a guarantee, that the file is
used in the proper context.
-- Christian
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
prev parent reply other threads:[~2004-05-28 10:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-21 16:32 Alain Frisch
2004-05-21 18:11 ` Richard Jones
2004-05-21 18:27 ` Nicolas Cannasse
2004-05-26 8:32 ` Xavier Leroy
2004-05-26 15:12 ` Nicolas Cannasse
2004-05-28 0:33 ` Alain Frisch
2004-05-28 1:54 ` Jacques GARRIGUE
2004-05-28 7:13 ` Nicolas Cannasse
2004-05-28 9:55 ` Alain Frisch
2004-05-28 10:14 ` Christian Lindig [this message]
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=D2D3D30E-B08F-11D8-8801-000A95DDB608@cs.uni-sb.de \
--to=lindig@cs.uni-sb.de \
--cc=caml-list@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