From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@inria.fr
Subject: Parallelized parsing
Date: Mon, 20 Apr 2009 22:15:27 +0100 [thread overview]
Message-ID: <200904202215.27735.jon@ffconsultancy.com> (raw)
I'm desperately trying to prepare for the imminent drop of a rock-solid
multicore-friendly OCaml implementation and was wondering what work has been
done on parallelized parsers and/or parallel-friendly grammars?
For example, Mathematica syntax for nested lists of integers looks like:
{{{1, 2}}, {{3, 4}, {4, 5}}, ..}
and there are obvious divide-and-conquer approaches to lexing and parsing that
grammar. You can recursively subdivide the string (e.g. memory mapped from a
file) to build a tree of where the tokens { , and } appear by index and then
recursively convert the tree into an AST.
What other grammars can be lexed and/or parsed efficiently in parallel?
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next reply other threads:[~2009-04-20 21:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 21:15 Jon Harrop [this message]
2009-04-20 21:35 ` [Caml-list] " Mike Lin
2009-04-21 0:52 ` Yitzhak Mandelbaum
2009-04-21 15:55 ` Jon Harrop
2009-04-21 1:44 ` Polymorphism problem Eliot Handelman
2009-04-21 8:50 ` [Caml-list] " Mauricio Fernandez
2009-04-21 7:19 ` [Caml-list] Parallelized parsing David MENTRE
2009-04-21 16:04 ` Jon Harrop
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=200904202215.27735.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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