From: art yerkes <ayerkes@speakeasy.net>
To: caml-list@inria.fr
Subject: [Caml-list] Some questions about using code from the O'caml compiler
Date: Tue, 30 Sep 2003 00:32:55 -0500 [thread overview]
Message-ID: <20030930003255.363ab234.ayerkes@speakeasy.net> (raw)
I'm just about to finish a type reflector for camlp4. It allows camlp4 modules
to receive correct information about the types of expressions in the input
code.
Currently, I am using the parser from the parsing directory of the compiler to
yield a core_type_desc to the camlp4 code, which works well. I intend to release
the type reflector under a mixture of Q Public License (the original license for
the files copied from O'caml), and LGPL for the code that I added.
Of course, all of the files copied from O'caml are clearly marked so.
Is this ok, or should I write my own parser, and parsetree types?
--
"Should array indices start at 0 or 1? My compromise of 0.5 was rejected
without, I thought, proper consideration."
- S. Kelly-Bootle
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
reply other threads:[~2003-09-30 5: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=20030930003255.363ab234.ayerkes@speakeasy.net \
--to=ayerkes@speakeasy.net \
--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