From: "Issac Trotts" <ijtrotts@ucdavis.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] Development versions: ocamlconf, ASPCC
Date: Tue, 2 Mar 2004 21:16:11 -0800 [thread overview]
Message-ID: <20040303051611.GA1204@manzanita> (raw)
In-Reply-To: <20040303014757.GA23400@tallman.kefka.frap.net>
On Tue, Mar 02, 2004 at 05:47:57PM -0800, Kenneth Knowles wrote:
> Hello caml-list,
>
> I have two projects that I haven't polished to a release state, but I'm hoping
> someone might be interested in, so I'm offering access via darcs
> (http://www.abridgegame.org/darcs)
>
> (1) ocamlconf
> Ocamlconf is like autoconf but much simpler, utterly ocaml-centric, and
> dependent on findlib.
>
> You can get it via the command
> 'darcs get http://kefka.frap.net:8080/~kenn/repos/ocamlconf'
I guess you mean David's Advanced Revision Control System. I had never
heard of this before your post. There is no Debian package for this,
though it looks like a useful program.
I wonder if Darcs could be modified to explicitly keep track of changes
to the ASTs of OCaml source files...
> What it is/does:
> * An autoconf-like tool but using ocaml scripts instead of m4
> * It uses the ocaml toplevel instead of bytecode for cross-version
> compatability
> * Outputs a makefile and a simple config.ml
Could it output an OCaml script instead of a makefile? It would
probably be easier to read, debug, and modify.
> * It is _extremely_ simple to use, especially if your projects are 100% ocaml,
> like mine. (A configure.ml comparable to a configure.ac might be 100
> lines for a complex project)
>
> Why I didn't use autotools/ocamlmakefile/...:
> * autotools are pretty C centric, and more of a pain than necessary for
> an ocaml project which already limits its audience to more-or-less modern
> users. GNU must support very arcane and archaic setups, but ocamlconf aims
> to suport "anything with ocaml"
> * anyone building an ocaml package with have the toplevel already
> * OcamlMakefile is awkward with multiple targets (such as suites of utilities)
> and I'd rather write (or depend on) a simple ocaml script than a complex
> Makefile
> * And of course, I did it to see if I could make something simple and useful
> for myself - I've succeeded, as it is what I use for 100% of my ocaml
> projects
Thank you!
--
Issac Trotts
http://redwood.ucdavis.edu/~issac
-------------------
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
next prev parent reply other threads:[~2004-03-03 5:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 1:47 Kenneth Knowles
2004-03-03 5:16 ` Issac Trotts [this message]
2004-03-03 6:25 ` Kenneth Knowles
2004-03-03 19:53 ` Issac Trotts
2004-03-03 23:06 ` Kenneth Knowles
2004-03-03 19:56 ` David MENTRE
2004-03-03 20:29 ` Issac Trotts
2004-03-03 22:36 ` Kenneth Knowles
2004-03-11 11:09 ` Markus Mottl
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=20040303051611.GA1204@manzanita \
--to=ijtrotts@ucdavis.edu \
--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;
as well as URLs for NNTP newsgroup(s).