caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Martin Berger <martinb@dcs.qmul.ac.uk>
To: skaller@ozemail.com.au
Cc: caml-list@inria.fr, Martin Berger <martinb@dcs.qmul.ac.uk>
Subject: Re: [Caml-list] Building large and portable projects
Date: Sat, 22 Nov 2003 14:32:55 +0000	[thread overview]
Message-ID: <3FBF7397.9030608@dcs.qmul.ac.uk> (raw)
In-Reply-To: <1069431167.5426.45.camel@pelican>

> Make systems are all conceptually wrong.

agreed.

> This leads to the first novel idea. Fixpoints.
> Interscript is based on that idea.

> A build system does NOT have targets. 

> A build systems has processes and files.
> Lets call the processes ARROWS and the files OBJECTS.

> Oh. That's a category. We allow of course,
> products of files (multiple outputs and inputs)
> and sums of files (choose one of several).
> [And of course we'd better make it cartesian
> closed and allow processes to be files .. 
> called scripts .. :]

this is a fascinating proposal. i have two immediate questions:

* as someone else pointed out, relying on convergence towards
   fixpoints may be too strong. some build processes may
   never converge, rather they evenually stabilise in some
   "open ball", so you might need some (user supplied) notion
   of "close enough". how do you do that?

* according to [1], a cartesian closed category with fixpoints
   and finite sums is equivalent to the category with one object
   and one arrow. how do you deal with this?

martin

[1] Hagen Huwig and Axel Poigne, A note on inconsistencies caused
by fixpoints in a cartesian dosed category, Theoretical Computer
Science 73 (1990), p. 101-112.

-------------------
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


  parent reply	other threads:[~2003-11-22 14:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 18:47 Martin Jambon
2003-11-20 19:56 ` sylvain.le-gall
2003-11-21  1:45   ` Nicolas Cannasse
2003-11-21  5:25     ` David Brown
2003-11-21  5:48       ` Nicolas Cannasse
2003-11-21  6:45         ` David Brown
2003-11-21  6:49         ` sylvain.le-gall
2003-11-21 16:12           ` skaller
2003-11-21 17:53             ` Eric Dahlman
2003-11-22 14:45               ` skaller
2003-11-21 19:04             ` sylvain.le-gall
2003-11-22 14:34               ` skaller
2003-11-22 18:50                 ` sylvain.le-gall
2003-11-22 14:32             ` Martin Berger [this message]
2003-11-22 14:55               ` skaller
2003-11-22 17:08             ` David Brown
2003-11-22 16:48               ` skaller
2003-11-23  3:25               ` Nicolas Cannasse
2003-11-23  4:29                 ` David Brown
2003-11-23 17:21                 ` skaller
2003-11-22 17:13             ` David Brown
2003-11-24 18:02             ` Ken Rose
2003-11-24 19:04               ` Christian Lindig
2003-11-21 16:32           ` Martin Jambon
2003-11-21 18:57             ` sylvain.le-gall
2003-11-21  9:14       ` Christian Lindig
2003-11-21  9:28 ` Richard Jones
2003-11-21 15:35 ` skaller
2003-11-21 17:05 ` Jason Hickey
2003-11-21 18:55   ` sylvain.le-gall
2003-11-21 19:30     ` [Caml-list] Omake [Was: Building large and portable projects] Aleksey Nogin
2003-11-21 20:39       ` Damien
2003-11-22  3:30         ` Aleksey Nogin
2003-11-21 23:48       ` sylvain.le-gall
2003-11-22  1:32         ` Nicolas Cannasse
2003-11-22  3:51         ` Aleksey Nogin
2003-11-28 16:29   ` [Caml-list] Building large and portable projects David Brown

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=3FBF7397.9030608@dcs.qmul.ac.uk \
    --to=martinb@dcs.qmul.ac.uk \
    --cc=caml-list@inria.fr \
    --cc=skaller@ozemail.com.au \
    /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).