From: skaller <skaller@ozemail.com.au>
To: Martin Berger <martinb@dcs.qmul.ac.uk>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Building large and portable projects
Date: 23 Nov 2003 01:55:00 +1100 [thread overview]
Message-ID: <1069512900.6703.32.camel@pelican> (raw)
In-Reply-To: <3FBF7397.9030608@dcs.qmul.ac.uk>
On Sun, 2003-11-23 at 01:32, Martin Berger wrote:
> > Make systems are all conceptually wrong.
> * 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?
In interscript I have an iteration limit.
In a GUI system, one pass per mouse click I guess.
> * 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.
Ouch. First, the concept above is to use categories
as an inspirational model, but we do have to layer
the abstraction on real storage/execution systems,
so that theoretical constraint is unlikely to the most
difficult problem :-)
Second .. well, Ocaml uses this model 'as inspiration'
as well, and it's authors know a good deal more theory
than me so they're more likely to be able to answer :-)
Yeah, both answers are a cop-out (meaning I don't know :-)
-------------------
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
next prev parent reply other threads:[~2003-11-22 15:55 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
2003-11-22 14:55 ` skaller [this message]
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=1069512900.6703.32.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=caml-list@inria.fr \
--cc=martinb@dcs.qmul.ac.uk \
/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