caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Rogoff <bpr@best.com>
To: Mattias Waldau <mattias.waldau@abc.se>
Cc: caml-list@inria.fr
Subject: Re: Why is Ocaml better than Java (WAS: [Caml-list] ocaml complexity)
Date: Fri, 8 Jun 2001 14:39:49 -0700 (PDT)	[thread overview]
Message-ID: <Pine.BSF.4.21.0106081430070.27414-100000@shell5.ba.best.com> (raw)
In-Reply-To: <AAEBJHFJOIPMMIILCEPBCEBCCMAA.mattias.waldau@abc.se>

On Fri, 8 Jun 2001, Mattias Waldau wrote:
> The real questions is how to convince a Java-programmer to start using
> Ocaml.
> 
> The arguments I can list is:
...
> - closures (however can always be programmed using local class with
> ()-method)
> - better typechecking makes higher order functions simple to use (however, I
>   think that a local class in Java will be as good)
...

- block structure with lexical scope

C derived languages are relatively flat; yeah you can have nested scopes
but you can't nest function definitions. I hate that. Pascal derived
languages are much nicer in this respect, but they always have
restrictions on what you can do with functions. So ML style closures will 
be a lot nicer than Java style closures faked with objects since you don't 
have to explicitly make the local variables into arguments. 

I'll post an example if you wish, but I sent one to compl.lang.ml a few
months ago when some Python programmer was asking for examples of what
you could do in ML that you couldn't easily do in Python. I think Python 
is fixed now, but Java is still broken. So is C++ (sorry Chris, couldn't 
resist ;-).

-- Brian


-------------------
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


  parent reply	other threads:[~2001-06-08 21:39 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-07  8:58 [Caml-list] ocaml complexity leary
2001-06-07 18:29 ` Jonathan Coupe
2001-06-08  9:41   ` leary
2001-06-08 10:05     ` Why is Ocaml better than Java (WAS: [Caml-list] ocaml complexity) Mattias Waldau
2001-06-08 13:31       ` Pierre Weis
2001-06-08 16:37         ` William Chesters
2001-06-08 21:39       ` Brian Rogoff [this message]
     [not found]       ` <Pine.BSF.4.21.0106081430070.27414-100000@shell5.ba.best.co m>
2001-06-08 22:16         ` Chris Hecker
2001-06-08 12:27     ` [Caml-list] ocaml complexity Jonathan Coupe
2001-06-08 20:22       ` Chris Hecker
2001-06-08 20:31         ` Miles Egan
2001-06-08 22:17           ` Jonathan Coupe
2001-06-08 22:18             ` Miles Egan
2001-06-11 14:05             ` Pierre Weis
2001-06-09 19:41           ` John Max Skaller
2001-06-08 22:59         ` David Fox
2001-06-09  0:43         ` leary
2001-06-09  1:09           ` Mark Wotton
2001-06-09  8:36           ` Markus Mottl
2001-06-09 20:58           ` John Max Skaller
2001-06-08 22:46       ` leary
2001-06-09  1:18         ` David Fox
2001-06-12 14:17           ` John Max Skaller
2001-06-13 15:21             ` Brian Rogoff
2001-06-13 20:32               ` leary
2001-06-13 22:58                 ` Johann Höchtl
2001-06-13 21:18               ` John Max Skaller
2001-06-09 22:32         ` Jonathan Coupe
2001-06-11  0:20           ` leary
2001-06-08 10:15 Why is Ocaml better than Java (WAS: [Caml-list] ocaml complexity) Dave Berry
2001-06-11 19:36 Jean-Marc Eber

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=Pine.BSF.4.21.0106081430070.27414-100000@shell5.ba.best.com \
    --to=bpr@best.com \
    --cc=caml-list@inria.fr \
    --cc=mattias.waldau@abc.se \
    /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).