caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Markus Mottl <markus@mail4.ai.univie.ac.at>
To: Bruce Hoult <bruce@hoult.org>
Cc: caml-list@inria.fr
Subject: Re: "Re: [Caml-list] A G'Caml question" + additional info
Date: Wed, 11 Jul 2001 21:12:52 +0200	[thread overview]
Message-ID: <20010711211251.A24340@fichte.ai.univie.ac.at> (raw)
In-Reply-To: <a05101015b7722efaf2d3@[128.135.227.93]>; from bruce@hoult.org on Wed, Jul 11, 2001 at 11:35:16 -0500

On Wed, 11 Jul 2001, Bruce Hoult wrote:
> But the language itself seems to be starting to rival C++ for sheer
> complexity. When you want to do something you seem to have a choice
> of using this feature, or *this* one, or *this* newly developed one.

Having choices is not necessarily bad, being forced to using many
alternatives is. I think that OCaml has succeeded quite well so far in
keeping different features apart as one can see in the standard library,
which can be used with the core language + modules alone. I hope this
will stay so!

Whether one or the other feature will be thrown out at some point of
time depends on how it performs in real work. That's not necessarily
easily tried in small scale experiments.

> Dylan is conceptually a much simpler language, with less intimidating 
> syntax, and you can easily express what you want to do using a very 
> small number of basic constructs.

Maybe, I don't know. But it does not declare itself as a research
language.  Everybody who uses OCaml should be aware of its status. If
you use experimental features, this is likely to burn you some time
in the future. If you stay with the core + module language, you should
probably be fairly safe for the foreseeable future.

Regards,
Markus Mottl

-- 
Markus Mottl                                             markus@oefai.at
Austrian Research Institute
for Artificial Intelligence                  http://www.oefai.at/~markus
-------------------
Bug reports: http://caml.inria.fr/bin/caml-bugs  FAQ: http://caml.inria.fr/FAQ/
To unsubscribe, mail caml-list-request@inria.fr  Archives: http://caml.inria.fr


  reply	other threads:[~2001-07-11 19:13 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-11 14:30 Krishnaswami, Neel
2001-07-11 16:22 ` Brian Rogoff
2001-07-11 16:35   ` Bruce Hoult
2001-07-11 19:12     ` Markus Mottl [this message]
2001-07-12  3:15   ` Patrick M Doane
  -- strict thread matches above, loose matches on Subject: below --
2001-07-16 18:24 John R Harrison
2001-07-10 18:21 Krishnaswami, Neel
2001-07-11  6:09 ` Sven
     [not found] <3B3D503C.E91DDE34@ozemail.com.au>
2001-06-30 16:01 ` Patrick M Doane
2001-06-30 20:59   ` Brian Rogoff
2001-07-01  5:32     ` Patrick M Doane
2001-07-02 15:55       ` Brian Rogoff
2001-07-10 18:08         ` Patrick M Doane
     [not found] <3B3BB6EC.3DEB6CBF@ozemail.com.au>
2001-06-29  4:18 ` Patrick M Doane
2001-06-20  3:16 [Caml-list] A G'Caml question Brian Rogoff
2001-06-25 17:11 ` "Re: [Caml-list] A G'Caml question" + additional info Jun Furuse
2001-06-28  2:21   ` Patrick M Doane
2001-06-28  4:40     ` Brian Rogoff

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=20010711211251.A24340@fichte.ai.univie.ac.at \
    --to=markus@mail4.ai.univie.ac.at \
    --cc=bruce@hoult.org \
    --cc=caml-list@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;
as well as URLs for NNTP newsgroup(s).