From: skaller <skaller@ozemail.com.au>
To: Richard Jones <rich@annexia.org>
Cc: Mattias Waldau <mattias.waldau@abc.se>, caml-list@pauillac.inria.fr
Subject: Re: [Caml-list] Commercial application written in O'Caml: ExcelEverywhere
Date: 21 Sep 2003 05:32:22 +1000 [thread overview]
Message-ID: <1064086341.2679.66.camel@pelican> (raw)
In-Reply-To: <20030919144701.GB4205@redhat.com>
On Sat, 2003-09-20 at 00:47, Richard Jones wrote:
> On Fri, Sep 19, 2003 at 10:01:15AM +0200, Mattias Waldau wrote:
> > Disadvantage
> > - 8-bits strings.
> > UNICODE is needed and the standard for .NET, Java, Ruby...
>
> Yeah, UTF-8 is a real necessity for us too.
>
> > - Few libraries
>
> Yup. If there's one thing which Perl/Java have taught us, it's that
> you can NEVER, EVER have a large enough standard library! It'd be
> great if OCaml came with a really comprehensive library.
I don't agree entirely. As a member of the C++ Standardisation
Committee I can tell you that one aim is to keep the C++ Standard
Library sensibly sized. A library which is too large becomes
unmaintable, too daunting for users .. and demonstrates that the
language fails to support simplicity.
One virtue of the Ocaml library at the moment is that after
certain 'weird' libraries are removed from consideration,
the data-structures and algorithms part is quite small,
the core language support is tiny, and the external functionality
wrappers (such as Unix) are modest and sensible in their scope.
What Ocaml lacks, in my opinion, isn't a 'larger library' so much
as a suitable packaging mechanism to make it easy to obtain
and install add-on libraries. And whilst the Hump is a nice
source of codes, it isn't quite the same as CPAN :)
-------------------
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-09-20 19:32 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 16:11 [Caml-list] possible typechecker bug Fernando Alegre
2003-09-19 2:00 ` malc
2003-09-19 2:06 ` Fernando Alegre
2003-09-19 6:57 ` Julien Signoles
2003-09-19 8:01 ` [Caml-list] Commercial application written in O'Caml: ExcelEverywhere Mattias Waldau
2003-09-19 9:26 ` Benjamin Geer
2003-09-20 8:12 ` Damien Doligez
2003-09-19 11:10 ` skaller
2003-09-19 14:49 ` Richard Jones
2003-09-19 15:02 ` Remi Vanicat
2003-09-19 17:20 ` Karl Zilles
2003-09-20 19:25 ` skaller
2003-09-20 20:28 ` Benjamin Geer
2003-09-21 11:55 ` skaller
2003-09-21 15:01 ` [Caml-list] how can I print graphics on my local printer under Linux? PL
[not found] ` <20030921161556.GA451@swordfish>
2003-09-22 8:10 ` PL
2003-09-22 8:38 ` Basile Starynkevitch
2003-09-23 20:24 ` Christophe TROESTLER
2003-09-23 21:48 ` Pierre Weis
2003-09-22 9:21 ` Olivier Andrieu
2003-09-19 22:29 ` [Caml-list] Commercial application written in O'Caml: ExcelEverywhere Oleg Trott
2003-09-20 9:09 ` Mattias Waldau
2003-09-20 9:25 ` Jean-Marc Eber
2003-09-21 9:38 ` Xavier Leroy
2003-09-20 20:01 ` skaller
2003-09-20 19:58 ` skaller
2003-09-19 11:48 ` Ville-Pertti Keinonen
2003-09-20 18:53 ` skaller
2003-09-20 19:31 ` Alain.Frisch
2003-09-19 14:47 ` Richard Jones
2003-09-20 19:32 ` skaller [this message]
2003-09-19 16:23 ` kknowles
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=1064086341.2679.66.camel@pelican \
--to=skaller@ozemail.com.au \
--cc=caml-list@pauillac.inria.fr \
--cc=mattias.waldau@abc.se \
--cc=rich@annexia.org \
/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).