From: briand@aracnet.com
To: Jacques GARRIGUE <garrigue@kurims.kyoto-u.ac.jp>
Cc: jrouquiethearchiveshouldhaveafewantispamtricks@ens-lyon.fr,
caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Re : [path directives]
Date: Wed, 25 Aug 2004 11:54:03 -0700 [thread overview]
Message-ID: <16684.57419.984058.252036@soggy.deldotd.com> (raw)
In-Reply-To: <20040824.105432.78379156.garrigue@kurims.kyoto-u.ac.jp>
>>>>> "Jacques" == Jacques GARRIGUE <garrigue@kurims.kyoto-u.ac.jp> writes:
Jacques> The basic reason is that there are two files to read:
Jacques> const.cmo and const.cmi, and they are loaded by two
Jacques> independent mechanisms. const.cmo must be loaded
Jacques> explicitly by a #load command, but const.cmi is searched
Jacques> automatically in the path when a Const.xxx identifier is
Jacques> used. The independence of the two mechanisms may be
Jacques> confusing, but you may understand it better if you think of
Jacques> loading a .cma file: in that case, you really don't know
Jacques> where the corresponding .cmi should be.
I understand the separation of implementation vs interface, however it
seems that a reasonable default it to use the path of the cma file to
find the cmi before giving up.
However if the mechanisms are _completely_ separate then I can see
where that would be a problem, and I believe that is what your are
saying (?)
Thanks
Brian
-------------------
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
next prev parent reply other threads:[~2004-08-25 18:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 20:27 briand
2004-08-23 20:36 ` [Caml-list] Re : [path directives] Jean-Baptiste Rouquier
2004-08-24 1:41 ` briand
2004-08-24 1:54 ` Jacques GARRIGUE
2004-08-25 18:54 ` briand [this message]
2004-08-24 9:09 ` [Caml-list] Damien Doligez
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=16684.57419.984058.252036@soggy.deldotd.com \
--to=briand@aracnet.com \
--cc=caml-list@pauillac.inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=jrouquiethearchiveshouldhaveafewantispamtricks@ens-lyon.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