From: "Ian Zimmerman" <nobrowser@gmail.com>
To: "OCaml Mailing List" <caml-list@inria.fr>
Cc: "Denis Bueno" <dbueno@gmail.com>, omake@metaprl.org
Subject: Re: [Caml-list] Scripting in ocaml
Date: Tue, 26 Dec 2006 18:36:45 -0500 [thread overview]
Message-ID: <17af13780612261536x5f5f0d93sb1eb6ecef1b22598@mail.gmail.com> (raw)
In-Reply-To: <45915860.6030806@metaprl.org>
On 12/26/06, Aleksey Nogin <nogin@metaprl.org> wrote:
> Not quite scripting in OCaml, but related - the OMake build system comes
> with its own shell interpreter - osh. The language is not OCaml, but
> it's a functional language that was _specifically_ designed as a
> scripting language, so I would argue that writing scripts in osh is more
> convenient that scripting in OCaml (although, of course, for somebody
> already familiar with OCaml, learning osh might be a bit harder that
> learning some hypothetical scripting extension of OCaml).
>
> Note that if the goal is specifically "scripts to perform various build-
> and development-related tasks" as you've mentioned, then I would
> definitely suggest looking at OMake and osh - there the scripting
> language is the same as the build specification language and you can
> inline osh scriplets directly into "make-style" build rules of OMake.
Does it handle building in general, or just OCaml-based projects? For example,
can it deduce header dependencies for a C file - possibly with a
plugin, like cons
or scons? I couldn't use one OMake for building OCaml projects and
make for others.
Ian
next prev parent reply other threads:[~2006-12-26 23:36 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-21 3:41 Denis Bueno
2006-12-21 4:34 ` [Caml-list] " Erik de Castro Lopo
2006-12-21 7:22 ` skaller
2006-12-21 9:12 ` Till Varoquaux
2006-12-21 9:18 ` Chad Perrin
2006-12-21 10:29 ` skaller
2006-12-21 20:21 ` Chad Perrin
2006-12-21 13:30 ` Serge Aleynikov
2006-12-21 13:52 ` skaller
2006-12-21 14:59 ` Serge Aleynikov
2006-12-21 20:25 ` Chad Perrin
2006-12-21 20:41 ` Daniel Bünzli
2006-12-21 22:16 ` Chad Perrin
2006-12-22 12:21 ` strong/weak typing terminology (was Re: [Caml-list] Scripting in ocaml) Daniel Bünzli
2006-12-22 16:51 ` Tom
2006-12-22 17:34 ` Daniel Bünzli
2006-12-22 18:16 ` skaller
2006-12-22 18:47 ` Daniel Bünzli
2006-12-22 19:42 ` skaller
2006-12-22 20:03 ` David Brown
2006-12-22 20:17 ` Chad Perrin
2006-12-23 3:48 ` skaller
2006-12-23 4:11 ` Chad Perrin
2006-12-22 20:19 ` Chad Perrin
2006-12-23 12:58 ` Daniel Bünzli
2006-12-23 16:06 ` Chad Perrin
2006-12-23 21:50 ` Tom
2006-12-26 6:10 ` Chad Perrin
2006-12-22 20:14 ` Chad Perrin
2006-12-21 21:11 ` [Caml-list] Scripting in ocaml Serge Aleynikov
2006-12-21 21:27 ` Philippe Wang
2006-12-21 22:06 ` Serge Aleynikov
2006-12-22 12:35 ` Jon Harrop
2006-12-21 22:19 ` Chad Perrin
2006-12-22 12:37 ` Jon Harrop
2006-12-22 18:52 ` Chad Perrin
2006-12-22 2:51 ` skaller
2006-12-22 15:20 ` Jon Harrop
2006-12-22 11:32 ` Jon Harrop
2006-12-23 18:50 ` Jon Harrop
2006-12-24 0:15 ` Serge Aleynikov
2006-12-24 3:30 ` skaller
2006-12-21 14:59 ` Richard Jones
2006-12-21 20:27 ` Chad Perrin
2006-12-21 23:35 ` Martin Jambon
2006-12-26 17:14 ` Aleksey Nogin
2006-12-26 23:36 ` Ian Zimmerman [this message]
2006-12-27 18:25 ` Aleksey Nogin
2006-12-27 18:39 ` Richard Jones
2006-12-27 19:20 ` Aleksey Nogin
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=17af13780612261536x5f5f0d93sb1eb6ecef1b22598@mail.gmail.com \
--to=nobrowser@gmail.com \
--cc=caml-list@inria.fr \
--cc=dbueno@gmail.com \
--cc=omake@metaprl.org \
/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