caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Brian Hurt <bhurt@spnz.org>
To: Blue Prawn <fmonnier@linux-nantes.fr.eu.org>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] what is high-level (was: Wikipedia)
Date: Fri, 4 Nov 2005 09:13:40 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.63.0511040900470.1006@localhost.localdomain> (raw)
In-Reply-To: <200511041443.15429.fmonnier@linux-nantes.fr.eu.org>



On Fri, 4 Nov 2005, Blue Prawn wrote:

> Hello,
>
> Perhaps it would be a good idea to create un page on Wikipedia to 
> explain what is a high-level programming language,

As near as I can figure, the definition is simple.  Assembly language is 
not a high level language.  Everything else is.

http://www.webopedia.com/TERM/C/C.html

>From that link:
> Although it is a high-level language, C is much closer to assembly 
> language than are most other high-level languages.

In other words, all languages are high-level, some are just more 
high-level than others.


> because its definition in all documents related to OCaml definitively do 
> not fit the definition the penguins gave to me when I started to go in 
> my lug, which was a language easy to learn and use designed for common 
> users, and not only for programers and computer scientists. They told me 
> about ABC which led to python which is comonly used in softwares as 
> scripting extention for the users. But OCaml do need some background 
> knowledge to understand the official manual, which is not true for PHP, 
> Python or Ruby.

OK, here's the thing: Ocaml is a different paradigm than Python, Ruby, and 
PHP.  If you know Pascal, C, Fortran, etc., then learning PHP isn't 
difficult, because it too is a procedural language.  If you know C++, 
Java, etc., then learning Python or Ruby isn't that hard, because they're 
Object Oriented languages too.  If you already know SML or Haskell, 
learning Ocaml wouldn't be that hard.  The problem is that most people 
don't know SML or Haskell.

Learning a new paradigm is hard.  As someone who has done it three times 
now (moving from the sphagetti code of Basic to the procedural style of 
Pascal, then moving to Object Oriented, and most recently Functional), 
trust me on this.  Learning a new paradigm makes learning a new language 
10 times as hard AT LEAST as learning a new language in the old paradigm.

Brian


  reply	other threads:[~2005-11-04 15:10 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 [this message]
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
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=Pine.LNX.4.63.0511040900470.1006@localhost.localdomain \
    --to=bhurt@spnz.org \
    --cc=caml-list@inria.fr \
    --cc=fmonnier@linux-nantes.fr.eu.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).