caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David Teller <David.Teller@ens-lyon.org>
To: OCaml <caml-list@yquem.inria.fr>
Subject: Re: [Caml-list] what is high-level
Date: Fri, 04 Nov 2005 16:14:58 +0000	[thread overview]
Message-ID: <1131120898.6558.15.camel@titania> (raw)
In-Reply-To: <436B871A.40906@synopsys.com>

Le vendredi 04 novembre 2005 à 11:06 -0500, Alan Falloon a écrit : 
> David Teller wrote:
> 
> >Still, in OCaml/Haskell/ML, you do need some understanding of the type
> >system, which is typically not necessary in other programming languages.
> 
> To write software you need to have some notion of types. By that I mean 
> that you need an understanding of what values a certain operation can 
> produce.

Sure. But in Python/Boo, as you mention, you have duck typing. In my
books, that makes it easier to learn Python than OCaml, because that's
one less thing you need to know before starting your first program.

Of course, in OCaml, you have "static duck typing" for objects, but
that's a different issue.


> I think the biggest barrier is the language. It took me forever to 
> figure out what a 'row variable' was. 

Er... what is a row variable ? :)
Is that a polymorphic variant ?

> What we really need is a concept map from the popular languages (C, C++, 
> Java, Python, Perl) to OCaml. Show common idioms in those languages and 
> how they look in OCaml, and if there is a better way in OCaml then show 
> that too. It might not make a good Wikipedia article, but it is the sort 
> of project well suited to a Wiki. Is there an OCaml Wiki?

Iirc, there's an OCaml Wikibook on the Wikipedia.

Cheers,
 David
> 
-- 
Read, Write, and Publish Standard eBooks
  Free, Open Software, Open Standards and multi-platform
    The OpenBerg project http://www.openberg.org


  parent reply	other threads:[~2005-11-04 16:15 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-03 17:26 Wikipedia Jon Harrop
2005-11-03 19:24 ` [Caml-list] Wikipedia Gerd Stolpmann
2005-11-04  2:31   ` skaller
2005-11-04 13:46     ` [Caml-list] what is high-level (was: Wikipedia) Blue Prawn
2005-11-04 15:13       ` Brian Hurt
2005-11-04 15:28         ` David Teller
2005-11-04 16:02           ` skaller
2005-11-04 16:06           ` [Caml-list] what is high-level Alan Falloon
2005-11-04 16:10             ` William D. Neumann
2005-11-04 16:14             ` David Teller [this message]
2005-11-05  0:29             ` skaller
2005-11-05 22:05               ` Michael Walter
2005-11-06 14:28                 ` skaller
2005-11-04 16:50         ` Matt Gushee
2005-11-03 19:30 ` [Caml-list] Wikipedia Kip Macy
2005-11-03 20:46   ` Matt Gushee
2005-11-03 21:08     ` Mike Lin
2005-11-03 21:16 ` Florian Weimer
2005-11-04 17:15 ` Thomas Fischbacher
2005-11-04 21:05   ` Alex Goldman
2005-11-04 21:53     ` Gerd Stolpmann
2005-11-04 22:24       ` Alex Goldman
2005-11-06 19:32 ` Thomas Fischbacher
2005-11-07  6:44   ` Tony Edgin
2005-11-07 12:23     ` Thomas Fischbacher
2005-11-07 12:55       ` skaller
2005-11-07 13:03         ` Thomas Fischbacher

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=1131120898.6558.15.camel@titania \
    --to=david.teller@ens-lyon.org \
    --cc=caml-list@yquem.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).