From: Jacques GARRIGUE <garrigue@kurims.kyoto-u.ac.jp>
To: briand@aracnet.com
Cc: jrouquiethearchiveshouldhaveafewantispamtricks@ens-lyon.fr,
caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Re : [path directives]
Date: Tue, 24 Aug 2004 10:54:32 +0900 (JST) [thread overview]
Message-ID: <20040824.105432.78379156.garrigue@kurims.kyoto-u.ac.jp> (raw)
In-Reply-To: <16682.40154.269687.344133@soggy.deldotd.com>
From: briand@aracnet.com
> Why doesn't the load fail or give some indication of a problem ?
>
> Why doesn't caml know to look in the same directory which const.cmo
> came from ?
>
> I think I'll take a look through the sources and try and understand
> why this isn't more user friendly.
The basic reason is that there are two files to read: const.cmo and
const.cmi, and they are loaded by two independent mechanisms.
const.cmo must be loaded explicitly by a #load command, but const.cmi
is searched automatically in the path when a Const.xxx identifier is
used.
The independence of the two mechanisms may be confusing, but you may
understand it better if you think of loading a .cma file: in that
case, you really don't know where the corresponding .cmi should be.
Jacques Garrigue
-------------------
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-24 1: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 [this message]
2004-08-25 18:54 ` briand
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=20040824.105432.78379156.garrigue@kurims.kyoto-u.ac.jp \
--to=garrigue@kurims.kyoto-u.ac.jp \
--cc=briand@aracnet.com \
--cc=caml-list@pauillac.inria.fr \
--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;
as well as URLs for NNTP newsgroup(s).