From: Dario Teixeira <darioteixeira@yahoo.com>
To: "Hezekiah M. Carty" <hcarty@atmos.umd.edu>,
Berke Durak <berke.durak@exalead.com>
Cc: Caml-list List <caml-list@inria.fr>,
David Teller <David.Teller@univ-orleans.fr>
Subject: Re: [Caml-list] OSR - "Batteries included" - Standardizing syntax extensions and extra libraries
Date: Tue, 4 Mar 2008 20:31:38 +0000 (GMT) [thread overview]
Message-ID: <331303.21401.qm@web54606.mail.re2.yahoo.com> (raw)
In-Reply-To: <3a360f590803040950raa7eb1clcf0b8b1cc6a8edc7@mail.gmail.com>
> If ocamlfind were included as a standard part of the community OCaml
> distribution, then I think it would ease this process significantly.
Hi,
Indeed. I was about to start my own OSR thread concerning the proper
use of ocamlfind with libraries that offer a syntax extension. One
good example is PG'OCaml (by Rich Jones): it ships with a META file
that makes the use of the syntax extension really simple with findlib.
This is the META file: (I just removed the description lines)
name="pgocaml"
version="1.0"
requires="unix,extlib,csv,pcre,calendar"
archive(byte)="pgocaml.cma"
archive(native)="pgocaml.cmxa"
package "statements" (
requires = "pgocaml,camlp4"
version = "1.0"
archive(syntax,preprocessor) = "pa_pgsql.cmo"
archive(syntax,toploop) = "pa_pgsql.cmo"
)
Notice the "statements" subpackage. Suppose you have a "test.ml" file
that uses PG'OCaml's syntax extension. Compiling it with findlib is
as simple as:
ocamlfind ocamlc -package pgocaml.statements -syntax camlp4o -c test.ml
This is of course particularly relevant for GODI, and I noticed that not
all GODI packages ship with camlp4-friendly META files (Sexplib, for one).
Moreover, it would be nice if a standard name could be found for these
subpackages. PG'OCaml uses "statements", but that may be a bit long-winded.
What about just "pp"?
Now, to reach package nirvana, we just need to get Ocamlbuild to be
friendlier to findlib -- including in the use of these syntax extensions.
Cheers,
Dario Teixeira
__________________________________________________________
Sent from Yahoo! Mail.
A Smarter Inbox. http://uk.docs.yahoo.com/nowyoucan.html
next prev parent reply other threads:[~2008-03-04 20:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 17:12 Berke Durak
2008-03-04 17:50 ` [Caml-list] " Hezekiah M. Carty
2008-03-04 20:27 ` Sylvain Le Gall
2008-03-04 20:55 ` [Caml-list] " David Teller
2008-03-04 21:14 ` Hezekiah M. Carty
2008-03-04 22:35 ` Paolo Donadeo
2008-03-04 22:57 ` Lukasz Stafiniak
2008-03-04 20:31 ` Dario Teixeira [this message]
2008-03-05 0:30 ` [Caml-list] " Ed Keith
2008-03-05 2:29 ` Yaron Minsky
2008-03-05 8:57 ` [Caml-list] OSR - "Batteries included" - Standardizing syntaxextensions " David Allsopp
2008-03-05 12:02 ` [Caml-list] OSR - "Batteries included" - Standardizing syntax extensions " Gerd Stolpmann
2008-03-05 15:04 ` Richard Jones
2008-03-05 0:10 ` Richard Jones
2008-03-05 10:19 ` Berke Durak
2008-03-05 11:41 ` Alain Frisch
2008-03-05 12:36 ` Bünzli Daniel
2008-03-05 14:03 ` Dario Teixeira
2008-03-06 14:21 ` Jim Miller
2008-03-05 15:43 ` Stefano Zacchiroli
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=331303.21401.qm@web54606.mail.re2.yahoo.com \
--to=darioteixeira@yahoo.com \
--cc=David.Teller@univ-orleans.fr \
--cc=berke.durak@exalead.com \
--cc=caml-list@inria.fr \
--cc=hcarty@atmos.umd.edu \
/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