From: j h woodyatt <jhw@conjury.org>
To: caml-list@yquem.inria.fr
Subject: Re: examples using parser combinator in Pagoda CF library?
Date: Tue, 1 Nov 2005 21:54:16 -0800 [thread overview]
Message-ID: <20C6B0F9-BB65-4035-B6DF-0CA7C1431820@conjury.org> (raw)
In-Reply-To: <20051102054504.1EA1CD464@yquem.inria.fr>
On 01 Nov 2005, at 21:45, caml-list-request@yquem.inria.fr wrote:
>
> I'm currently using ocamlex and ocamlyacc but have recently
> heard of parser combinators. Searching the net I found the
> Pagoda Core Foundation library which has this:
>
> http://www.wetware.com/jhw/src/pagoda/doc/cf/Cf_parser.html
>
> Its obviously nice to have documentation, but its also nice to
> have working examples. Anyone have any?
The newest versions of this code are in the OCaml Network Application
Environment (NAE) project on SourceForge.Net:
<http://sourceforge.net/projects/ocnae/>
You should look at the Cf_uri module for an example of how to use the
Cf_parser combinators.
--james
next parent reply other threads:[~2005-11-02 7:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20051102054504.1EA1CD464@yquem.inria.fr>
2005-11-02 5:54 ` j h woodyatt [this message]
2005-11-02 1:27 Examples " Erik de Castro Lopo
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=20C6B0F9-BB65-4035-B6DF-0CA7C1431820@conjury.org \
--to=jhw@conjury.org \
--cc=caml-list@yquem.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).