From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on yquem.inria.fr X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=AWL autolearn=disabled version=3.1.3 Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id 3C12EBBAF for ; Fri, 17 Oct 2008 13:15:11 +0200 (CEST) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AosEABwQ+EjAXQIniGdsb2JhbACTKz4CFiKlHn+HNAEDAQODaQ X-IronPort-AV: E=Sophos;i="4.33,431,1220220000"; d="scan'208";a="30453576" Received: from concorde.inria.fr ([192.93.2.39]) by mail4-smtp-sop.national.inria.fr with ESMTP; 17 Oct 2008 13:15:10 +0200 Received: from mail3-relais-sop.national.inria.fr (mail3-relais-sop.national.inria.fr [192.134.164.104]) by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id m9HBFA8X026184 (version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=OK) for ; Fri, 17 Oct 2008 13:15:10 +0200 X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AuEBAFcQ+EhIDtyblGdsb2JhbACTKz4CAgkJDAcRA6Ucf4c0AQMBA4Np X-IronPort-AV: E=Sophos;i="4.33,431,1220220000"; d="scan'208";a="18214614" Received: from fg-out-1718.google.com ([72.14.220.155]) by mail3-smtp-sop.national.inria.fr with ESMTP; 17 Oct 2008 13:15:09 +0200 Received: by fg-out-1718.google.com with SMTP id e21so355004fga.25 for ; Fri, 17 Oct 2008 04:15:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to :subject:mime-version:content-type:content-transfer-encoding :content-disposition; bh=E1LTCrpAqoAoxalZUSjVEjXtavJWJaPm89091vuC22M=; b=BgQ+76ePIlJHIIqVoMV4cU9u4UGiP8FUXNFNjSJpMiMeio8wc5brIVbuoCGjxagANN fMWrQQfHYEp4aKe50IoBUdWpDz7yGSCrRYr00/G7U7igv4R6PqLQ59i/E2l5sjM/144p YbDempQSuXG5M0E0C46YCN9B8MjxsENKpZyfU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:mime-version:content-type :content-transfer-encoding:content-disposition; b=QIj2TrEfHRr8HpyWVfdR85OK2Pvwbh1a7zaZhuFjmU11kTyzVfobvC+cWSZmJM+1Vv R3joM1sKsDd4J9AxEfLLRN8WmsRo9825XeYCKATJrO+31cgc3hOFXx8M2BE1+4Mcrz22 3esMcue1OqkgWkKAS+UOb8Bom+EExtqaXwccY= Received: by 10.86.4.14 with SMTP id 14mr3789252fgd.20.1224242108115; Fri, 17 Oct 2008 04:15:08 -0700 (PDT) Received: by 10.86.2.19 with HTTP; Fri, 17 Oct 2008 04:15:08 -0700 (PDT) Message-ID: Date: Fri, 17 Oct 2008 12:15:08 +0100 From: "Conglun Yao" To: caml-list@inria.fr Subject: Camlp4 generate more than one (compiled) files? MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Miltered: at concorde with ID 48F873BE.000 by Joe's j-chkmail (http://j-chkmail . ensmp . fr)! X-Spam: no; 0.00; camlp:01 camlp:01 compiler:01 cmo:01 syntax:01 preprocess:01 cmo:01 compiled:04 compiled:04 separately:05 extend:07 i'm:09 yao:09 wondering:09 file:11 Dear all, I'm just wondering is it possible to use camlp4 to generate more than one compiled files. Normally, camlp4 preprocesses a file and then pass it directly to compiler (for *.cmo), or its pretty-printer (for *.ml or other 'plain' file). In my case, I want to extend the syntax, and write a file, then preprocess (camlp4) it to generate two different *.cmo files, each one could be executed separately. Is it possible? Thanks, Conglun