From: "Yaron Minsky" <yminsky@cs.cornell.edu>
To: "Damien" <Damien.Pous@ens-lyon.fr>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] : YaM
Date: Sat, 24 Apr 2004 08:56:07 -0400 (EDT) [thread overview]
Message-ID: <2891.192.168.0.101.1082811367.squirrel@minsky-primus.homeip.net> (raw)
In-Reply-To: <20040424124424.3eedba7c.Damien.Pous@ens-lyon.fr>
Damien said:
> On Sat, 24 Apr 2004 01:56:43 +0200 Markus Mottl wrote:
>
>> It also features file digests, compilation command digests, etc., but
>> can do this in the general case, i.e. is very similar to "make".
>
> I didn't checked back, but it seems to me that omake does not feature
> "compilation command digests" :
>
> if you change the makefile (switch a debug flag for some files...)
> - with omake/make... : make clean all
> - with YaM : ./YaM (compiles only affected files + link phases)
omake has the right behavior. If the command changes, then the affected
targets are rebuilt. It's actually an amazingly cool feature. No more
wondering if my system is up to date after modifying the makefile!
> however the major improvements against omake are
> - better native/bytecode interaction : no Makefile to edit in order to
> switch,
> - fine -pack support
> (but I tend to believe I'm the only one finding -pack useful...)
I wonder if -pack support could be added by modifying OMakeroot. One of
the things I like about omake is that it isn't ocaml-specific -- instead
it's a well thought-out general-purpose solution. It's not complete yet,
but my experience with it has been quite good.
-------------------
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
prev parent reply other threads:[~2004-04-24 12:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-22 7:02 Damien
2004-04-23 23:56 ` Markus Mottl
2004-04-24 10:44 ` Damien
2004-04-24 12:56 ` Yaron Minsky [this message]
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=2891.192.168.0.101.1082811367.squirrel@minsky-primus.homeip.net \
--to=yminsky@cs.cornell.edu \
--cc=Damien.Pous@ens-lyon.fr \
--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).