From: Alessandro Baretta <alex@baretta.com>
To: Sven Luther <luther@dpt-info.u-strasbg.fr>, Ocaml <caml-list@inria.fr>
Subject: Re: [Caml-list] camlimages vs. labltk
Date: Wed, 26 Mar 2003 10:00:03 +0100 [thread overview]
Message-ID: <3E816C13.7040507@baretta.com> (raw)
In-Reply-To: <20030326083345.GA2985@iliana>
Sven Luther wrote:
> On Wed, Mar 26, 2003 at 09:25:48AM +0100, Alessandro Baretta wrote:
>
>
> There is already the -pack option, and the right thing to solve this
> problem would be to build all libraries to make usage of it (if
> possible). So you would have a CamlImage.Image module and a Labltk.Image
> module, which work pretty well.
>
> Now, library writters just need to modify their build system to take
> advantage of it, starting by the INRIA released libraries, especially
> the ones provided by the ocaml tarball directly like labltk.
Sven, someone on this list wisely pointed out that you buy
nothing by telling someone else "You don't need that
feature". We do need namespaces. It might not be paramount:
I'm pretty sure there is something more important to be done
at Inria. But, please, don't tell me that -pack will cure
cancer, promote democracy, establish universal peace, and
make my teeth look whiter. Packing does not allow
factorizing your code--bytecode, actually--in small reusable
units. One big .cmo is not as flexible as a .cma. I simply
might not want to link all of a library: what if it's
modules contain side-effects? So -pack is good, but
namespaces are still a necessary feature to Ocaml as to any
industrial level programming language.
Cheers to all Caml riders,
Alex
-------------------
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-03-26 8:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-25 19:33 Shivkumar Chandrasekaran
2003-03-26 8:25 ` Alessandro Baretta
2003-03-26 8:33 ` Sven Luther
2003-03-26 9:00 ` Alessandro Baretta [this message]
2003-03-26 10:50 ` Sven Luther
2003-03-26 11:24 ` Alessandro Baretta
2003-03-26 11:38 ` Sven Luther
2003-03-26 19:08 ` Chris Hecker
2003-03-26 21:08 ` Alessandro Baretta
2003-03-27 17:23 ` David Brown
2003-03-27 19:46 ` Chris Hecker
2003-03-28 5:33 ` Alessandro Baretta
2003-03-28 5:35 ` David Brown
2003-03-28 14:10 ` Damien Doligez
2003-03-28 15:00 ` Sven Luther
2003-03-30 10:06 ` Damien Doligez
2003-03-30 10:38 ` Sven Luther
2003-04-01 14:14 ` [Caml-list] naming conflicts (was: camlimages vs. labltk) Damien Doligez
2003-04-01 15:05 ` Benjamin C. Pierce
2003-04-01 19:51 ` Chris Hecker
2003-04-08 10:33 ` Damien Doligez
2003-03-31 1:21 ` [Caml-list] camlimages vs. labltk Chris Hecker
2003-03-30 9:26 ` Alessandro Baretta
2003-03-26 18:49 ` Shivkumar Chandrasekaran
2003-03-26 10:48 ` Stefano Zacchiroli
2003-03-26 10:55 ` Sven Luther
2003-03-26 14:10 ` Stefano Zacchiroli
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=3E816C13.7040507@baretta.com \
--to=alex@baretta.com \
--cc=caml-list@inria.fr \
--cc=luther@dpt-info.u-strasbg.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