caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alessandro Baretta <a.baretta@barettadeit.com>
To: Alain Frisch <Alain.Frisch@inria.fr>, Ocaml <caml-list@inria.fr>,
	metaocaml-hackers-l@cs.rice.edu
Subject: Re: [Caml-list] Namespace clash
Date: Thu, 09 Feb 2006 12:12:49 +0100	[thread overview]
Message-ID: <43EB23B1.8070801@barettadeit.com> (raw)
In-Reply-To: <43EACE5C.4010804@inria.fr>

Alain Frisch wrote:
> Alessandro Baretta wrote:
> 
>> Probably, all that ocaml lacks to properly handle namespacing is a 
>> -open directive, telling the compiler to imply a "open Xxxx" at the 
>> beginning of all .ml and .mli files on the command line. Given this 
>> compiler flag, the build system could take care of everything.
> 

I had not thought about this... Actually, it is not a bad idea, at least, in my 
build system. Ideally, the build system would have to have a way of mangling the 
library namespace by packaging up findlib-managed libraries in a single package. 
Then, it would have to isse the desired -open directives to an ad-hoc camlp4 
syntax extension. It's a bit of a hack, but it could work. I wonder if it is 
general enough a solution to become mainstream, though.

Alex

-- 
*********************************************************************

Ing. Alessandro Baretta

Studio Baretta
http://studio.baretta.com/

Consulenza Tecnologica e Ingegneria Industriale
Technological Consulting and Industrial Engineering

tel. +39 02 370 111 55
fax. +39 02 370 111 54


  reply	other threads:[~2006-02-09 11:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-08 13:28 Alessandro Baretta
2006-02-08 23:41 ` [Caml-list] " Jonathan Roewen
2006-02-09  5:08 ` Alain Frisch
2006-02-09 11:12   ` Alessandro Baretta [this message]
2006-02-09 14:52     ` Damien Doligez
2006-02-09 19:32 yoann padioleau

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=43EB23B1.8070801@barettadeit.com \
    --to=a.baretta@barettadeit.com \
    --cc=Alain.Frisch@inria.fr \
    --cc=caml-list@inria.fr \
    --cc=metaocaml-hackers-l@cs.rice.edu \
    /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).