From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Blair Zajac <blair@orcaware.com>
Cc: caml-list@inria.fr, ocaml-pxp-users <ocaml-pxp-users@orcaware.com>
Subject: [Caml-list] Re: [Ocaml-pxp-users] Announcement: PXP 1.1.94 (development version)
Date: 23 Jun 2003 16:09:23 +0200 [thread overview]
Message-ID: <1056377363.29686.5.camel@ares> (raw)
In-Reply-To: <3EF600F8.B1026D7B@orcaware.com>
Am Son, 2003-06-22 um 21.18 schrieb Blair Zajac:
> Gerd Stolpmann wrote:
> >
> > Hi list,
> >
> > I have just released a new development version of PXP. This
> > is a big change:
> >
> > The Pxp_reader module has been completely rewritten. This fixes some
> > problems with relative URLs.
> >
> > Pxp_yacc has been split up into four modules: Pxp_tree_parser contains
> > now the parser API returning object trees, Pxp_dtd_parser is the parser
> > API returning DTDs, Pxp_ev_parser is the event-based API, and
> > Pxp_core_parser is the core of the parser. Pxp_yacc is still available
> > as compatibility API. As part of the module redesign, Pxp_types includes
> > now parts of its interface from Pxp_core_types_type. I hope this style
> > of programming is comprehensible.
> >
> > I think PXP can now compiled with CVS releases of O'Caml.
> >
> > It is now possible to turn warnings into errors.
> >
> > The event-based parser can now preprocess namespaces. Furthermore, there
> > are normalization filters.
> >
>
> Hi Gerd,
>
> Has the API changed to Pxp_reader, or will most PXP users will not
> notice this change?
I think most users will not notice the change. I have tried to be as
compatible as possible with previous versions, but there are some corner
cases where the new implementation behaves differently. This is
intentional, as the new implementation tries to fix "conceptual bugs".
The new signature of Pxp_reader is slightly different, but I hope this
does not matter for anybody.
>
> > The new version can be found at the usual place:
> >
> > http://www.ocaml-programming.de/packages/pxp-1.1.93.tar.gz
>
> Do you mean
>
> http://www.ocaml-programming.de/packages/pxp-1.1.94.tar.gz
Yes, of course. Just copying old mails is sometimes a bad idea.
Gerd
--
------------------------------------------------------------
Gerd Stolpmann * Viktoriastr. 45 * 64293 Darmstadt * Germany
gerd@gerd-stolpmann.de http://www.gerd-stolpmann.de
------------------------------------------------------------
-------------------
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
prev parent reply other threads:[~2003-06-23 14:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 15:52 [Caml-list] " Gerd Stolpmann
2003-06-22 19:18 ` [Caml-list] Re: [Ocaml-pxp-users] " Blair Zajac
2003-06-23 14:09 ` Gerd Stolpmann [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=1056377363.29686.5.camel@ares \
--to=info@gerd-stolpmann.de \
--cc=blair@orcaware.com \
--cc=caml-list@inria.fr \
--cc=ocaml-pxp-users@orcaware.com \
/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).