caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alessandro Baretta <alex@baretta.com>
To: "Yurii A. Rashkovskii" <yrashk@openeas.org>, ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] module namespace
Date: Wed, 06 Nov 2002 17:27:10 +0100	[thread overview]
Message-ID: <3DC942DE.2050008@baretta.com> (raw)
In-Reply-To: <20021106141751.GE24776@rashko>



Yurii A. Rashkovskii wrote:
> Moin Andreas!
> 
> Andreas Rossberg schrieb am Wednesday, den 06. November 2002:
> 
> 
>>Oz uses URIs to identify and locate modules. By default, the system
>>recognizes file:, http: and x-oz: schemes, the latter denoting the
>>standard library. Module management is programmable however, so that it
>>may be extended to handle other schemes/protocols.
> 
> 
> BTW, it's a nice idea. Most probably next release of OCamlNS will
> deprecate my style of namespaces (Org.Ocaml.[...]) and let namespace
> be "proto://..." and I'll develop ocamlnsc and ocamlnsopt that will
> use namespace URLs to get the modules (even via http) and pass them
> to ocamlc|ocamlopt (in way like ocamlfind). I don't know whether this
> feature is demanded by ocaml users community, but for me it looks
> very attractive and probably I'll use it my project. 
> 
> In my thoughts I think that URL should point to a kinda textual
> module description (with dependencies and so on).

I think this is a very cool feature. It has some interesting 
  implications which must be worked out first. Consider the 
case where the user is not connected to the same service 
that provides the package. A portable computer user, for 
example, or simply someone wishing to install from 
disk-based source distribution. There must be an alternative 
way of resolving packages. One solution might be defining a 
CAMLPATH environment variable à la Java CLASSPATH, and 
looking for the modules in 
<camlpath_directory>/<ns_url_path> before actually 
attempting a network connection.

Finally, a really cool, cool, cool feature would be dynamic 
linking of Ocaml modules from their namespace URL, with 
static typechecking at compile time against the 
corresponding .mli files. How do you like this idea, Yurii?

Alex

-------------------
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


  reply	other threads:[~2002-11-06 16:27 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-02  0:24 Yurii A. Rashkovskii
2002-11-02  8:51 ` Alessandro Baretta
2002-11-02 16:10   ` Yurii A. Rashkovskii
2002-11-02 16:34     ` Alessandro Baretta
2002-11-02 16:57       ` Chris Hecker
2002-11-02 17:20       ` Yurii A. Rashkovskii
2002-11-02 17:40         ` Alessandro Baretta
2002-11-02 19:14           ` Yurii A. Rashkovskii
2002-11-02 22:37       ` Lauri Alanko
2002-11-04  8:07         ` Alessandro Baretta
2002-11-05 16:27           ` Jeffrey Palmer
2002-11-05 22:30             ` Alessandro Baretta
2002-11-06 10:30             ` Andreas Rossberg
2002-11-06 14:17               ` Yurii A. Rashkovskii
2002-11-06 16:27                 ` Alessandro Baretta [this message]
2002-11-06 16:56                   ` Yurii A. Rashkovskii
2002-11-06 19:30                     ` Christian Lindig
2002-11-06 20:36                       ` Alessandro Baretta

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=3DC942DE.2050008@baretta.com \
    --to=alex@baretta.com \
    --cc=caml-list@inria.fr \
    --cc=yrashk@openeas.org \
    /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).