From: Christian Lindig <lindig@ips.cs.tu-bs.de>
To: caml-list@pauillac.inria.fr
Subject: scanning and parsing short strings
Date: Thu, 10 Jul 1997 16:42:52 +0200 (MET DST) [thread overview]
Message-ID: <199707101442.QAA15363@infbsst5.ips.cs.tu-bs.de> (raw)
[sorry - no french version]
Dear Caml enthusiasts,
many applications rely on protocols which they must parse. This can
be either done ad hoc using regular expressions or scanner/parser
generated by Camllex/yacc. Which method is advisable when the scanned
items are relative short strings (< 100 Bytes)? In general I would
prefer to use Camllex/yacc specifications in order not distribute the
different parsers over the whole application. On the other hand start-up
time of the scanner/lexer may be too high when used for small strings
(Lexing.from_string). Any advice?
The background of my question: I like to implement a CGI library. There
are many headers that are passed to a CGI application that need to
be parsed. I already took a look at the MMM code which uses a mixed
approach.
Christian
--
Christian Lindig
lindig@ips.cs.tu-bs.de
next reply other threads:[~1997-07-11 19:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-07-10 14:42 Christian Lindig [this message]
1997-07-17 16:22 ` Francois Rouaix
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=199707101442.QAA15363@infbsst5.ips.cs.tu-bs.de \
--to=lindig@ips.cs.tu-bs.de \
--cc=caml-list@pauillac.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).