From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id KAA32119 for caml-red; Tue, 9 Jan 2001 10:04:43 +0100 (MET) 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 JAA00943 for ; Tue, 9 Jan 2001 09:05:29 +0100 (MET) Received: from localhost.localdomain (jimbo108.zip.com.au [202.7.88.108]) by nez-perce.inria.fr (8.11.1/8.10.0) with ESMTP id f0985PL12943 for ; Tue, 9 Jan 2001 09:05:26 +0100 (MET) Received: from ozemail.com.au (IDENT:root@localhost [127.0.0.1]) by localhost.localdomain (8.9.3/8.8.7) with ESMTP id TAA30646; Tue, 9 Jan 2001 19:03:40 +1100 Message-ID: <3A5AC5DC.213F3D51@ozemail.com.au> Date: Tue, 09 Jan 2001 19:03:40 +1100 From: John Max Skaller X-Mailer: Mozilla 4.7 [en] (X11; I; Linux 2.2.12-20 i686) X-Accept-Language: en MIME-Version: 1.0 To: Michael Hicks CC: Charles Martin , caml-list@inria.fr Subject: Re: Module hierarchies References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: weis@pauillac.inria.fr > > I am wondering how a large OCaml project might be structured, specifically > > in terms of directories and files. My solution is simple enough: I use a literate programming tool (interscript, see my sig below) to _generate_ all the Ocaml files in a scratch directory. So the structure of the program is defined in terms of the LP source files, which need to be related to the generated files. (It usually is though :-) The only problem I have with this is that ocamllex/yacc do not respect #line directives. -- John (Max) Skaller, mailto:skaller@maxtal.com.au 10/1 Toxteth Rd Glebe NSW 2037 Australia voice: 61-2-9660-0850 checkout Vyper http://Vyper.sourceforge.net download Interscript http://Interscript.sourceforge.net