From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Delivered-To: caml-list@yquem.inria.fr Received: from concorde.inria.fr (concorde.inria.fr [192.93.2.39]) by yquem.inria.fr (Postfix) with ESMTP id 3C3ACBCAB for ; Thu, 26 May 2005 12:06:07 +0200 (CEST) Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35]) by concorde.inria.fr (8.13.0/8.13.0) with ESMTP id j4QA66Tc027303 for ; Thu, 26 May 2005 12:06:07 +0200 Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id MAA10710 for ; Thu, 26 May 2005 12:06:06 +0200 (MET DST) Received: from mail.barettadeit.com (h213-255-109-130.albacom.net [213.255.109.130] (may be forged)) by nez-perce.inria.fr (8.13.0/8.13.0) with ESMTP id j4QA65XA030494 for ; Thu, 26 May 2005 12:06:06 +0200 Received: from [10.0.0.10] (alex.barettalocal.com [10.0.0.10]) by mail.barettadeit.com (Postfix) with ESMTP id 43393803754A for ; Thu, 26 May 2005 12:06:05 +0200 (CEST) Message-ID: <42959F7A.7020908@barettadeit.com> Date: Thu, 26 May 2005 12:05:46 +0200 From: Alex Baretta User-Agent: Debian Thunderbird 1.0.2 (X11/20050331) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Ocaml Subject: BCP relating to -pack? Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Miltered: at concorde with ID 42959F8E.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Miltered: at nez-perce with ID 42959F8D.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)! X-Spam: no; 0.00; baretta:01 -pack:01 cmo:01 -pack:01 compiler:01 patching:01 kloc:01 baretta:01 foresee:98 cmi:01 conflicts:01 modules:01 cma:01 hierarchy:01 directive:02 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on yquem.inria.fr X-Spam-Status: No, score=0.1 required=5.0 tests=FORGED_RCVD_HELO autolearn=disabled version=3.0.2 X-Spam-Level: The AS/Xcaml and FreerP projects are now getting big enough that namespace conflicts begin to emerge within them. We are thinking about changing our build system so as to encapsulate libraries as single cmo/cmi packages to introduce a hierarchy in the namespace. The problem I foresee is that the -pack directive to the compiler breaks the code, because all modules referring to module X within xyz.cma would need to open module Xyz. Patching the entire project is in my opinion contrary to the "a posteriori" approach to namespace management taken by the Caml team with the -pack directive. So here is my question. Has anyone already faced this kind of problem on a fairly large project ( ~ 100 kloc)? What are the Best Current Practices relating to -pack? Alex -- ********************************************************************* http://www.barettadeit.com/ Baretta DE&IT A division of Baretta SRL tel. +39 02 370 111 55 fax. +39 02 370 111 54 Our technology: The Application System/Xcaml (AS/Xcaml) The FreerP Project