From: Alan Schmitt <alan.schmitt@polytechnique.org>
To: Philippe Wang <mail@philippewang.info>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] use of ";;" when teaching Ocaml
Date: Tue, 23 Jun 2015 15:27:16 +0200 [thread overview]
Message-ID: <m2si9itv0r.fsf@charm-ecran.irisa.fr> (raw)
In-Reply-To: <CAAFfW_qOP7QNYec8fw5qC2_JA7Spc-N0P4SxHE8x3G9fXj3uJw@mail.gmail.com> (Philippe Wang's message of "Tue, 23 Jun 2015 01:41:45 +0200")
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Hello,
Thanks to everyone for your answers, this has given me much food for
thought.
On 2015-06-23 01:41, Philippe Wang <mail@philippewang.info> writes:
> In my opinion, it's a lot more relevant to use a very limited and very
> simple subset of OCaml when teaching to beginners. And this subset
> does not involve expressions at top-level because it's not worth the
> trouble.
I like this approach because it amounts to saying "one always starts
a phrase with 'let' or 'type'" (and later in the year there can be
'open', 'module', 'include'). I sure can live without top-level
expressions.
On the other hand, I also like the idea of terminating phrases, simply
because explaining when it terminates is not trivial otherwise, as
a 'let' may not be the beginning of a phrase.
> Also, using the interactive top-level loop is, in my opinion, not good
> for beginners. It should only be presented to those who already
> understand very well the "core" of OCaml. The most frequent issue with
> the top-level loop is that it gets in the way of the notion of
> compiling a program, and it might give the false impression that OCaml
> can be interpreted.
I am curious about this. My goal is to teach the language, and I find
that a REPL backed with a file works great to do this (using tuareg or
ocaml-top). What do you use to make sure students have a fast
compile/debug cycle?
Thanks again,
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
Weekly CO₂ average (2015-05-30, Mauna Loa Observatory): 403.41 ppm
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 472 bytes --]
next prev parent reply other threads:[~2015-06-23 13:27 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 13:31 Alan Schmitt
2015-06-22 13:52 ` Ivan Gotovchits
2015-06-22 13:53 ` Daniil Baturin
2015-06-22 14:19 ` Gerd Stolpmann
2015-06-22 15:48 ` Damien Doligez
2015-06-22 15:56 ` Thomas Refis
2015-06-22 16:07 ` Mark Shinwell
2015-06-22 16:30 ` Gerd Stolpmann
2015-06-22 16:47 ` Mark Shinwell
2015-06-22 17:08 ` Daniel Bünzli
2015-06-22 18:56 ` Gerd Stolpmann
2015-06-22 17:18 ` Török Edwin
2015-06-22 17:42 ` Francois Berenger
2015-06-22 17:46 ` Ivan Gotovchits
2015-06-22 17:53 ` John Whitington
2015-06-22 16:07 ` Pippijn van Steenhoven
2015-06-22 16:25 ` Daniel Bünzli
2015-06-22 18:18 ` Steve Zdancewic
2015-06-22 16:42 ` Thomas Refis
2015-06-22 16:47 ` David House
2015-06-22 17:08 ` Daniil Baturin
2015-06-22 17:04 ` Daniel Bünzli
2015-06-22 23:41 ` Philippe Wang
2015-06-23 1:15 ` Kenichi Asai
2015-06-23 13:27 ` Alan Schmitt [this message]
2015-06-23 13:35 ` Ivan Gotovchits
2015-06-23 13:36 ` Ivan Gotovchits
2015-06-25 16:51 ` Philippe Wang
2015-06-29 0:12 ` Philippe Wang
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=m2si9itv0r.fsf@charm-ecran.irisa.fr \
--to=alan.schmitt@polytechnique.org \
--cc=caml-list@inria.fr \
--cc=mail@philippewang.info \
/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