From: Sven LUTHER <luther@dpt-info.u-strasbg.fr>
To: Jacques Garrigue <garrigue@kurims.kyoto-u.ac.jp>
Cc: orodeh@cs.huji.ac.il, caml-list@inria.fr
Subject: Re: Ref syntax
Date: Fri, 22 Dec 2000 09:45:17 +0100 [thread overview]
Message-ID: <20001222094517.B486@lambda.u-strasbg.fr> (raw)
In-Reply-To: <20001222122938T.garrigue@kurims.kyoto-u.ac.jp>; from garrigue@kurims.kyoto-u.ac.jp on Fri, Dec 22, 2000 at 12:29:38PM +0900
On Fri, Dec 22, 2000 at 12:29:38PM +0900, Jacques Garrigue wrote:
> * have a notation to abbreviate the OCAMLLIB directory in include
> paths. One could write
> ocamlc -c -I +labltk -I +lablGL gears.ml
> rather than
> ocamlc -c -I `ocamlc -where`/labltk -I `ocamlc -where`/lablgGL gears.ml
Yes this is extremely usefull, and would be a necessity if you don't want
people to simply install all their stuff in the $OCAMLLIB directory, possibly
overwritting some future addition to the what is put in there by ocaml.
Also, what is the reason the current system does search in the $OCAMLLIB as
well as the current directory for files ? if this was so, we could simply
write :
ocamlc -c -I labltk -I lablGL gears.ml
and have ocamlc search in the following places (and in this order ?) :
$OCAMLLIB
$PWD
$PWD/labltk
$PWD/lablGL
$OCAMLLIB/labltk
$OCAMLLIB/lablGL
C does something similar with his include files ?
Also another related issue would be to be able to append a modules path
element to libraries when building them. (or maybe this is already possible
?).
It would go like this :
ocamlc -<some special flag> XXX -a foo.cmo bar.cmo -o xxx.cma
which would give would put the modules in the xxx.cma library as follows :
XXX.Bar
XXX.Foo
instead of :
Bar
Foo
Thus permitting people to reuse modules names in their libraries whitout
needing to be carefull with conflict with other similar module names.
Friendly,
Sven Luther
next prev parent reply other threads:[~2000-12-22 9:09 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-14 14:12 Type annotations Ohad Rodeh
2000-12-15 2:25 ` Jacques Garrigue
2000-12-21 12:50 ` Ref syntax Ohad Rodeh
2000-12-22 3:29 ` Jacques Garrigue
2000-12-22 8:45 ` Sven LUTHER [this message]
2000-12-23 0:30 ` John Prevost
2000-12-22 9:07 ` Pierre Weis
2000-12-22 9:30 ` Jacques Garrigue
2000-12-22 14:22 ` Pierre Weis
2000-12-22 19:24 ` Marcin 'Qrczak' Kowalczyk
2000-12-22 9:17 ` Pascal Brisset
2000-12-23 0:37 ` John Prevost
2000-12-22 16:40 ` Marcin 'Qrczak' Kowalczyk
2000-12-23 0:39 ` John Prevost
2000-12-25 21:58 ` Pierre Weis
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=20001222094517.B486@lambda.u-strasbg.fr \
--to=luther@dpt-info.u-strasbg.fr \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=orodeh@cs.huji.ac.il \
/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).