Hi Alessandro! On Wed, 06 Nov 2002, Alessandro Baretta wrote: > >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. > > 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 > / before actually > attempting a network connection. I've already thought of it and have an idea how to resolve this problem. It is basically matches yours (something like local-proxy). In fact, since a lot of my development goes at my home PC w/ only dialup, it is a very important thing for me, so this problem will be resolved at the best way :) > 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? Well, I like and will implement it soon. -- Regards, Yurii.