From: Dan Bensen <danbensen@att.net>
To: Goswin von Brederlow <goswin-v-b@web.de>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] extending user-defined polymorphic variant types
Date: Mon, 7 May 2012 11:55:09 -0700 (PDT) [thread overview]
Message-ID: <1336416909.25268.YahooMailRC@web180012.mail.gq1.yahoo.com> (raw)
In-Reply-To: <877gwokkep.fsf@frosties.localnet>
[-- Attachment #1: Type: text/plain, Size: 480 bytes --]
> What is your use case? What do you want to do?
I've been trying to combine camlp4 with OMeta.
(http://tinlizzie.org/ometa/)
The idea is to allow the user to extend the concrete
syntax of the parsing system itself for parsing
different kinds of data (terminals), then layer the
standard combinator syntax on top of it.
Maybe the user can define a regular variant type for
terminals and the combinator ast type can wrap it in
a single variant (e.g. `Reader of Read.ast).
[-- Attachment #2: Type: text/html, Size: 788 bytes --]
next prev parent reply other threads:[~2012-05-07 18:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 9:40 Dan Bensen
2012-05-07 11:37 ` Philippe Veber
2012-05-07 16:47 ` Goswin von Brederlow
2012-05-07 18:55 ` Dan Bensen [this message]
2012-05-07 20:17 ` Dan Bensen
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=1336416909.25268.YahooMailRC@web180012.mail.gq1.yahoo.com \
--to=danbensen@att.net \
--cc=caml-list@inria.fr \
--cc=goswin-v-b@web.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).