From: Sen Horak <sen.horak@gmail.com>
To: Oliver Bandel <oliver@first.in-berlin.de>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Stream parser/make_lexer
Date: Sun, 26 Jun 2005 15:25:36 +0200 [thread overview]
Message-ID: <a80eebd40506260625605331a6@mail.gmail.com> (raw)
In-Reply-To: <20050626121847.GA322@first.in-berlin.de>
Ok, but that still doesn't answer my question (on how to connect the
stdin channel to a <> compatible char stream).
> I sometimes used the Stream-Module.
> But in the last time I switched more to ocamllex/ocamlyacc.
> The reason is, that I find them a good tool for many things.
> But I didn't tried the camlp4-stuff. It may be more easy to
> write complicated parsers with thema and maybe more elegant.
The documentation says that the parser interface is no longer
supported by proper ocaml, so we need to preprocess with ocampp4.
> But one reason to use ocamllex/ocamlyacc is that they are
> similar to lex/yacc, and therfore, if programming in a
> commercial field, porting the Ocaml-software back to C
> (even if not really happy about this), is easier.
The parser interface seems to be a nice thing if you want to "script"
in ocaml - that is, if you want to write quick and dirty solutions to
problems that you would ordinarily do in Perl/PYthon etc.
Of course, if you want to write a more complex parser, it's better to
do it in lex/yacc.
SH
next prev parent reply other threads:[~2005-06-26 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-26 10:12 Sen Horak
2005-06-26 12:18 ` [Caml-list] " Oliver Bandel
2005-06-26 13:25 ` Sen Horak [this message]
2005-06-26 14:24 ` Oliver Bandel
2005-06-26 13:52 ` Virgile Prevosto
2005-06-27 11:24 ` Sen Horak
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=a80eebd40506260625605331a6@mail.gmail.com \
--to=sen.horak@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=oliver@first.in-berlin.de \
/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).