caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Alain Frisch <Alain.Frisch@inria.fr>
To: Alessandro Baretta <a.baretta@barettadeit.com>
Cc: OCaml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] Namespace clash
Date: Thu, 09 Feb 2006 06:08:44 +0100	[thread overview]
Message-ID: <43EACE5C.4010804@inria.fr> (raw)
In-Reply-To: <43E9F1EE.1070502@barettadeit.com>

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.

Couldn't you use the -pp option to achieve the same behavior?

-- Alain


  parent reply	other threads:[~2006-02-09  5:08 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 [this message]
2006-02-09 11:12   ` Alessandro Baretta
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=43EACE5C.4010804@inria.fr \
    --to=alain.frisch@inria.fr \
    --cc=a.baretta@barettadeit.com \
    --cc=caml-list@yquem.inria.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).