caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jean Krivine" <jean.krivine@gmail.com>
To: "Dario Teixeira" <darioteixeira@yahoo.com>
Cc: Adrien <camaradetux@gmail.com>,
	"Romain Beauxis" <toots@rastageeks.org>,
	caml-list@inria.fr
Subject: Re: Re : [Caml-list] Manipulating xml files withing ocaml
Date: Sun, 23 Nov 2008 12:03:05 -0700	[thread overview]
Message-ID: <dc2907b70811231103q76b9d9c0w4bdca5cbe24b2a77@mail.gmail.com> (raw)
In-Reply-To: <191215.17693.qm@web111504.mail.gq1.yahoo.com>

In my case I just want to parse a small xml file and I don't need to
check for consistency so I think xml-light is fine enough. Thank you
for the references though
J

On Sun, Nov 23, 2008 at 10:54 AM, Dario Teixeira
<darioteixeira@yahoo.com> wrote:
>> PXP may be a better choice. It's harder at first, but
>> not much and
>> could be worth the five additionnal minutes required to
>> learn it. It
>> handles unicode and is still maintained (among others).
>
> Indeed.  If you find yourself routinely having to deal with XML,
> and if you need more advanced features such as validating very
> complex DTDs, than learning PXP is well worth it (Xml-light
> will choke on all but the simplest DTDs).
>
> If you are doing heavy manipulation of XML and wished for a
> more "native" support in the language, then take a look at
> Cduce/Ocamlduce.
>
> Finally, if you just need to parse a simple XML file and this
> is a one-off event, then Xml-light is indeed the simplest option.
>
> Cheers,
> Dario Teixeira
>
>
>
>
>


  reply	other threads:[~2008-11-23 19:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-23 17:18 Romain Beauxis
2008-11-23 17:29 ` Jean Krivine
2008-11-23 17:35   ` Re : " Adrien
2008-11-23 17:54     ` Dario Teixeira
2008-11-23 19:03       ` Jean Krivine [this message]
2008-11-23 22:45         ` Jake Donham

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=dc2907b70811231103q76b9d9c0w4bdca5cbe24b2a77@mail.gmail.com \
    --to=jean.krivine@gmail.com \
    --cc=camaradetux@gmail.com \
    --cc=caml-list@inria.fr \
    --cc=darioteixeira@yahoo.com \
    --cc=toots@rastageeks.org \
    /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).