From: skaller <skaller@users.sourceforge.net>
To: Xavier Leroy <xavier.leroy@inria.fr>
Cc: Jacques GARRIGUE <garrigue@kurims.kyoto-u.ac.jp>,
jdh30@cam.ac.uk, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Large projects in OCaml
Date: 25 May 2004 05:24:18 +1000 [thread overview]
Message-ID: <1085426657.6065.297.camel@pelican.wigram> (raw)
In-Reply-To: <20040524162002.A19967@pauillac.inria.fr>
On Tue, 2004-05-25 at 00:20, Xavier Leroy wrote:
> > What matters to end-users is shared libraries
> > which Ocaml can't build at all. The real world out
> > there demands *components* they can plug together.
>
> The next time I read a sentence starting with "the real world", I
> think I'm going to scream.
Sorry .. I deserve it (scream away :)
> At any rate, your jump from shared libraries to components is a
> non-sequitur. Shared libraries are a spectacularly poor component
> model (no multiple interfaces, almost no dynamic discovery of
> interfaces, no distribution transparency of any kind, etc).
No dispute.
> A good component model for OCaml (and other languages): that would be
> interesting. Shared libraries for the sake of shared libraries: that
> isn't interesting in the least.
In Python, you can simply install PyOracle and go.
Do you really think there is any comparison between
that and recompiling Python????
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
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:[~2004-05-24 19:24 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-19 17:24 ramu ramamurthy
2004-05-19 21:33 ` Jon Harrop
2004-05-19 23:04 ` David J. Trombley
2004-05-20 16:31 ` Eric Stokes
2004-05-20 17:37 ` Jon Harrop
2004-05-20 20:30 ` Eric Stokes
2004-05-20 21:04 ` Jon Harrop
2004-05-20 21:41 ` Eric Stokes
2004-05-21 11:28 ` Jon Harrop
2004-05-21 12:49 ` Ville-Pertti Keinonen
2004-05-21 16:27 ` Jon Harrop
2004-05-24 3:07 ` Jacques GARRIGUE
2004-05-24 5:20 ` skaller
2004-05-24 12:14 ` Jacques GARRIGUE
2004-05-24 13:54 ` skaller
2004-05-24 14:20 ` Xavier Leroy
2004-05-24 16:48 ` Alex Baretta
2004-05-24 17:38 ` brogoff
2004-05-25 5:25 ` Alan Schmitt
2004-05-24 19:24 ` skaller [this message]
2004-05-24 19:52 ` Brandon J. Van Every
2004-05-24 14:20 ` Daniel Bünzli
2004-05-24 19:34 ` skaller
2004-05-24 16:49 ` james woodyatt
2004-05-19 21:38 ` Richard Jones
2004-05-20 8:46 ` skaller
2004-05-20 11:56 ` [Caml-list] A problem with nan sejourne kevin
2004-05-20 20:42 ` Jon Harrop
2004-05-20 22:24 ` David J. Trombley
2004-05-20 22:45 ` Damien Doligez
2004-05-20 13:10 ` [Caml-list] Large projects in OCaml Jon Harrop
2004-05-20 16:23 ` skaller
2004-05-20 6:35 ` David Monniaux
2004-05-20 7:17 ` Dustin Sallings
2004-05-25 7:26 Mattias Waldau
2004-05-25 19:07 ` Richard Jones
2004-05-25 19:54 ` Evan Martin
2004-05-26 6:57 ` skaller
2004-05-26 8:09 ` Richard Jones
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=1085426657.6065.297.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=garrigue@kurims.kyoto-u.ac.jp \
--cc=jdh30@cam.ac.uk \
--cc=xavier.leroy@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