caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Mike Lin <mikelin@MIT.EDU>
To: Basile STARYNKEVITCH <basile@starynkevitch.net>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] parsing XML configuration file
Date: Tue, 3 Dec 2002 11:56:20 -0500	[thread overview]
Message-ID: <25BEE70A-06E0-11D7-88AB-000393AE4242@mit.edu> (raw)
In-Reply-To: <15852.50696.988643.235558@hector.lesours>

>
> I'm currently using PXP for that purpose, but I might be wrong.
>
> Should I consider switching to other Ocaml XML parsers (in particular
> yaxpo) to parse such a file (whose DTD is fixed by me, and which is
> mostly a shallow tree, not a recursive one..).
>
> Yes I know my question is a bit vague, but I beg for advice.

Yaxpo is a nonvalidating parser, so if you require the DTD validation, 
you should keep using PXP. If you do not require the DTD validation, 
for parsing some flat XML stored in a file, there is no particular 
reason why you should switch, since PXP and Yaxpo both do this fine.

The only situation in general in which you really have to use Yaxpo 
instead of PXP is when you need to achieve weird control effects with 
stopping and restarting the parser; I don't think this is the case for 
you. Otherwise, the differences between the parsers are not that much. 
They have different styles of data models, which may be significant. 
Yaxpo has fewer dependencies. Because of all the CPS constructs Yaxpo 
uses internally, PXP is probably faster (although I haven't tested it).

-Mike

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


      reply	other threads:[~2002-12-03 16:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 14:56 Basile STARYNKEVITCH
2002-12-03 16:56 ` Mike Lin [this message]

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=25BEE70A-06E0-11D7-88AB-000393AE4242@mit.edu \
    --to=mikelin@mit.edu \
    --cc=basile@starynkevitch.net \
    --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).