From: "Mikkel Fahnøe Jørgensen" <mikkel@dvide.com>
To: Peter Hawkins <hawkinsp@cs.stanford.edu>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3
Date: Mon, 9 Feb 2009 23:55:24 +0100 [thread overview]
Message-ID: <caee5ad80902091455u7e09b52ale3cc318071f86cee@mail.gmail.com> (raw)
In-Reply-To: <caee5ad80902091445w245fc99fg4fb1838a41fdd0f9@mail.gmail.com>
2009/2/9 Mikkel Fahnøe Jørgensen <mikkel@dvide.com>:
> Regarding what is missing in ocaml build environment ...
I should add that one reason I chose to work with ocaml is also
because of its build environment. I links very efficiently with C code
and do link with object files. So it is not a self-contained
environment that would be difficult to use for systems programming.
This is very powerful. But it does have implications as I mentioned
before.
I'd also like to mention that I find ocamlbuild a very good tool - not
only for ocaml, but for building anything. That fact that you can
dynamically include dependency generators in the build based on
generated build products is outstanding. I hope it will get to used
more because many of the platform dependent unix tools used in
makefiles could be done in ocaml code instead in a portable way.
So I am just mentioning where I see areas for improvement, it is not
like I think everything is just bad.
Mikkel
next prev parent reply other threads:[~2009-02-09 22:55 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-06 16:11 David Rajchenbach-Teller
2009-02-07 14:21 ` [Caml-list] " Mikkel Fahnøe Jørgensen
2009-02-07 14:43 ` Sylvain Le Gall
2009-02-07 14:58 ` [Caml-list] " Jon Harrop
2009-02-07 15:13 ` Sylvain Le Gall
2009-02-07 16:13 ` [Caml-list] " Matthieu Dubuget
2009-02-07 19:30 ` David Rajchenbach-Teller
2009-02-07 21:13 ` Matthieu Dubuget
2009-02-09 9:36 ` Romain Bardou
2009-02-09 15:56 ` David Teller
2009-02-07 15:46 ` Paolo Donadeo
2009-02-09 9:32 ` Romain Bardou
2009-02-09 10:30 ` ocamlbuild documentation (was Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3) Daniel Bünzli
2009-02-09 11:51 ` Romain Bardou
2009-02-09 12:30 ` Daniel Bünzli
2009-02-09 12:52 ` Romain Bardou
2009-02-09 13:07 ` Daniel Bünzli
2009-02-09 13:22 ` Romain Bardou
2009-02-09 13:36 ` Daniel Bünzli
2009-02-09 13:59 ` Romain Bardou
2009-02-09 14:04 ` Romain Bardou
2009-02-09 14:37 ` Daniel Bünzli
2009-02-09 17:26 ` Kuba Ober
2009-02-09 18:28 ` Jon Harrop
2009-02-09 21:24 ` DooMeeR
2009-02-10 14:06 ` ocamlbuild documentation Jan Kybic
2009-02-10 14:27 ` [Caml-list] " Matthieu Dubuget
[not found] ` <87k57ywc0k.fsf@fel.cvut.cz>
2009-02-10 15:50 ` Matthieu Dubuget
2009-02-10 15:58 ` Daniel Bünzli
2009-02-09 18:38 ` ocamlbuild documentation (was Re: [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3) David Teller
2009-02-09 22:02 ` [Caml-list] Re: [ANN] OCaml Batteries Included, alpha 3 Peter Hawkins
2009-02-09 22:45 ` Mikkel Fahnøe Jørgensen
2009-02-09 22:55 ` Mikkel Fahnøe Jørgensen [this message]
2009-02-10 7:48 ` Stefano Zacchiroli
2009-02-10 13:22 ` Mikkel Fahnøe Jørgensen
2009-02-07 20:04 ` Daniel Bünzli
2009-02-08 17:22 ` [Caml-list] " Richard Jones
2009-02-09 8:57 ` David Allsopp
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=caee5ad80902091455u7e09b52ale3cc318071f86cee@mail.gmail.com \
--to=mikkel@dvide.com \
--cc=caml-list@yquem.inria.fr \
--cc=hawkinsp@cs.stanford.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