From: "David MENTRE" <david.mentre@gmail.com>
To: "Alain Frisch" <Alain.Frisch@inria.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [announce] XStream: streaming XML transformation
Date: Wed, 28 Jun 2006 18:23:17 +0200 [thread overview]
Message-ID: <3d13dcfc0606280923m2930398cw7346bb6b6f97e442@mail.gmail.com> (raw)
In-Reply-To: <44A29ED1.6000207@inria.fr>
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.
next prev parent reply other threads:[~2006-06-28 16:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-28 15:22 Alain Frisch
2006-06-28 16:23 ` David MENTRE [this message]
2006-06-28 16:40 ` [Caml-list] " Alain Frisch
2006-06-28 17:18 ` Richard Jones
2006-06-29 6:16 ` Alain Frisch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3d13dcfc0606280923m2930398cw7346bb6b6f97e442@mail.gmail.com \
--to=david.mentre@gmail.com \
--cc=Alain.Frisch@inria.fr \
--cc=caml-list@inria.fr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).