From: Kakadu <kakadu.hafanana@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: [Caml-list] Idea about parser
Date: Thu, 1 Dec 2011 12:23:09 +0400 [thread overview]
Message-ID: <CAGmVoG3byhDyg5jWWkkn4=r61Qb+Jh38OQQM+wYhuAh4tbboSg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 816 bytes --]
Hello!
How difficult is to create a tool described below?
This Tool will look at AST (maybe specific, with some restrictions; maybe a
syntax extendion of ML-like language) of parser (which uses combinators)
and will generate parsing code according next rules:
1) this parser-function parses a grammar with some ambiguities --- GLR
parser is a right choice
2) this parser-function
......................??????................................... ---
recursive descent is better.
3) this parser-function
.......................????...................................... --- we
should use LALR parser.
Now I have code examples which generate parsers of different types from
some DSL. AFAIU the main problems are:
1) how to build grammar from parser-combinators code?
2) how to analyze grammar?
Best wishes,
Kakadu
[-- Attachment #2: Type: text/html, Size: 1753 bytes --]
reply other threads:[~2011-12-01 8:23 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAGmVoG3byhDyg5jWWkkn4=r61Qb+Jh38OQQM+wYhuAh4tbboSg@mail.gmail.com' \
--to=kakadu.hafanana@gmail.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