From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <weis@pauillac.inria.fr>
X-Original-To: caml-list@yquem.inria.fr
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 D8FE1BB84
	for <caml-list@yquem.inria.fr>; Wed, 28 Jun 2006 18:23:19 +0200 (CEST)
Received: from pauillac.inria.fr (pauillac.inria.fr [128.93.11.35])
	by concorde.inria.fr (8.13.6/8.13.6) with ESMTP id k5SGNKN6014494
	for <caml-list@yquem.inria.fr>; Wed, 28 Jun 2006 18:23:20 +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 SAA21737 for <caml-list@pauillac.inria.fr>; Wed, 28 Jun 2006 18:23:19 +0200 (MET DST)
Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.201])
	by nez-perce.inria.fr (8.13.6/8.13.6) with ESMTP id k5SGNI8s008417
	for <caml-list@inria.fr>; Wed, 28 Jun 2006 18:23:18 +0200
Received: by nz-out-0102.google.com with SMTP id 18so1626433nzp
        for <caml-list@inria.fr>; Wed, 28 Jun 2006 09:23:17 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gFPZNX/+KumhuLMK4xolSNDKmBgPT0lohyWO1pLJpcs+7pYaAR7zp3tQH43GY0yTZsIVO+3fMwE1paVt+FXWmWYIhqY/l7/P0yb8qQu3ETGlP7+QVN5n/HAkICHu5t2TzgcwZ89kJNdALojHUB/GWLaNz+X88mYxHz44qZdO0xI=
Received: by 10.64.184.4 with SMTP id h4mr1549982qbf;
        Wed, 28 Jun 2006 09:23:17 -0700 (PDT)
Received: by 10.64.250.4 with HTTP; Wed, 28 Jun 2006 09:23:17 -0700 (PDT)
Message-ID: <3d13dcfc0606280923m2930398cw7346bb6b6f97e442@mail.gmail.com>
Date: Wed, 28 Jun 2006 18:23:17 +0200
From: "David MENTRE" <david.mentre@gmail.com>
To: "Alain Frisch" <Alain.Frisch@inria.fr>
Subject: Re: [Caml-list] [announce] XStream: streaming XML transformation
Cc: caml-list@inria.fr
In-Reply-To: <44A29ED1.6000207@inria.fr>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <44A29ED1.6000207@inria.fr>
X-j-chkmail-Score: MSGID : 44A2ACF6.000 on nez-perce : j-chkmail score : X : 0/20 1
X-Miltered: at concorde with ID 44A2ACF8.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Miltered: at nez-perce with ID 44A2ACF6.000 by Joe's j-chkmail (http://j-chkmail.ensmp.fr)!
X-Spam: no; 0.00; frisch:01 frisch:01 ocaml:01 compiler:01 ocaml:01 bytecode:01 compares:01 ocamlduce:01 ocaml-:01 ocamlduce:01 2006:98 28,:98 caml-list:01 native:02 native:02 
X-Spam-Checker-Version: SpamAssassin 3.0.3 (2005-04-27) on yquem.inria.fr
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=RCVD_BY_IP autolearn=disabled 
	version=3.0.3

Hello Alain,

2006/6/28, Alain Frisch <Alain.Frisch@inria.fr>:
> Here's how XStream relates to OCaml: the compiler is written in OCaml
> and uses OCaml as a back-end to produce efficient native code. Moreover,
> XStream programs can embed OCaml code and manipulate OCaml values
> (useful to deal with non-XML data).

It seems obvious but I want to be sure: can XStream generated code be
embedded in OCaml programs (native and bytecode)?

How XStream compares to OCamlDuce? From what you said, XStream can
only do XML->XML or XML->OCaml transformation, no OCaml->XML
transformation. So XStream cannot be used as a replacement to
OCamlDuce. Is it correct?

Best wishes,
d.