Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
Camlp4 generate more than one (compiled) files?
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: 2008-10-17 (13:01)
From: Conglun Yao <yaoconglun@g...>
Subject: Re: [Caml-list] Camlp4 generate more than one (compiled) files?

Thanks for your reply.

What you mentioned in your blog:

In fact saving the AST into the cmo file is relatively simple: we just
turn it into a string (using Marshal) and write out the string as a
camlp4 substitution:
let bitmatch ext2sb = { ... }

becomes: let ext2sb = "<string containing marshalled representation of AST>"

If I understand correctly, the translated ext2sb would be kept in the
same cmo file(where the ext2sb is defined in the extended syntax),
rather than an additional (new) cmo file.

Currently I'm facing the problem that write a single file in extended
syntax, then camlp4 it into two different  cmo files.

e.g.   in, we define a type t

type myextend t =  * type definition in my extended syntax *

then I want to translate it into:


   type t =  * standard ocaml type definition *

  module T  and some t-related functions

and another file newFile.cmo :

   some functions which doesn't rely on type t,
   like checking the existence of some files (name mentioned in type
t's definition)

I know it's possible to generate the latter functions and pretty-print
them into, but don't know how to get a compiled cmo file



On Fri, Oct 17, 2008 at 12:52 PM, Richard Jones <> wrote:

> Camlp4 extensions can open and write files normally.  However it
> doesn't have access to crucial details of the 'OCaml environment' such
> as the current search path for libraries, which means that it usually
> cannot do anything sensible.
> For example, I wanted to load another module/library from a camlp4
> extension - but that sort of thing isn't possible as far as I can
> tell.
> I wrote a bit more about this issue here:
> Rich.
> --
> Richard Jones
> Red Hat