caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Brandon J. Van Every" <vanevery@indiegamedesign.com>
To: "caml" <caml-list@inria.fr>
Subject: [Caml-list] build tools with critical mass?
Date: Sun, 5 Sep 2004 13:28:51 -0700	[thread overview]
Message-ID: <OOEALCJCKEBJBIJHCNJDAELGHHAB.vanevery@indiegamedesign.com> (raw)

The discussion of build technologies is amusing... I can imagine all
sorts of wonderful problems I might try to solve, if only I didn't have
more pressing problems to solve.  :-)  The problem I'm more interested
in solving is deploying OCaml to a greater number of people.

So I have 2 questions regarding build tools.  Let's take it as a given
that GNU Make ain't so hot.  Do any of the alternatives have any
significant momentum behind them

- in the OCaml community?
- OUTSIDE OF the OCaml community?

My point being, perhaps the thing I'd throw my weight behind, is the
thing that's better than GNU Make that has the most people using it.  At
least, that's where I'd start looking for The Answer [TM].  Maybe there
is no One True Ansewr [TM], and we are doomed to a lifestyle of
fragmented build tools.  But I'd like to avoid that future if it is
possible.  I think widespread adoption of a language probably depends on
having a consistent set of build tools, at least for all the library
code one is typically going to grab.  As evidence I'd say that GNU Make
may not be great, but it is consistent and widespread.  So are Visual
Studio .sln files, or those of any other IDE that some chunk of
programmers 'prefer'.

Several years down the road, maybe the more experimental build tools
will gain enough adherants that they might become a basis for
industrialization of OCaml.  But right now, I think we need something
that's closer to being ready for prime time.  That, in my book, means
it's been used by a pile of people and the results are encouraging.  So,
what build tools fit this criterion?


Cheers,                         www.indiegamedesign.com
Brand*n Van Every               S*attle, WA

Praise Be to the caml-list Bayesian filter! It blesseth
my postings, it is evil crap!  evil crap!  Bigarray!
Unboxed overhead group!  Wondering!  chant chant chant...

Is my technical content showing?

// return an array of 100 packed tuples
temps
  int $[tvar0][2*100]; // what the c function needs
  value $[tvar1]; // one int
  value $[tvar2]; // one tuple
  int $[tvar3] // loop control var
oncePre
eachPre
  $[cvar0]=&($[tvar0][0]);
eachPost
  $[lvar0] = alloc(2*100, 0 /*NB: zero-tagged block*/ );
  for(int $[tvar3]=0;$[tvar3]<100;$[tvar3]++) {
    $[tvar2] = alloc_tuple(2);
    $[tvar1] = Val_int($[cvar0][0+2*$[tvar3]]);
    Store_field($[tvar2],0,$[tvar1]);
    $[tvar1] = Val_int($[cvar0][1]);
    Store_field($[tvar2],1,$[tvar1+2*$[tvar3]]);
    Array_store($[lvar0],$[tvar3],$[tvar0]);
  }
oncePost

-------------------
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:[~2004-09-05 20:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-05 20:28 Brandon J. Van Every [this message]
2004-09-06  2:02 ` chris.danx
2004-09-06  4:56   ` Brian Hurt
2004-09-06  9:21   ` skaller
2004-09-06 15:01     ` chris.danx

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=OOEALCJCKEBJBIJHCNJDAELGHHAB.vanevery@indiegamedesign.com \
    --to=vanevery@indiegamedesign.com \
    --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).