From: Ivan Gotovchits <ivg@ieee.org>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] use of ";;" when teaching Ocaml
Date: Mon, 22 Jun 2015 09:52:34 -0400 [thread overview]
Message-ID: <CALdWJ+w747WWwKL6KHu-tjpXWKNzR8Jw5Bx3vNvQ-Ux=E=pfkg@mail.gmail.com> (raw)
In-Reply-To: <m2vbefx41k.fsf@charm-ecran.irisa.fr>
[-- Attachment #1: Type: text/plain, Size: 1363 bytes --]
To my experience, this is a bad practice, that produces lots of confusion
to students.
They should clearly understand difference between writing code in a
toplevel and normal programming. A difference between
definition on a module level, and an expression. I usually say that `;;` is
not a part of a language, but just a part of a toplevel
command syntax (as well as toplevel directives), and strictly require not
to put `;;` in code.
On Mon, Jun 22, 2015 at 9:31 AM, Alan Schmitt <
alan.schmitt@polytechnique.org> wrote:
> Hello,
>
> In my Ocaml class, I tend to promote the use of ";;" to separate phrases
> (I'm basically following
>
> http://ocaml.org/learn/tutorials/structure_of_ocaml_programs.html#Usingandomittingand
> although I was not aware of this page when I created the course). My
> motivation is to minimize the difference between using the top-level and
> writing files.
>
> I am now wondering if this is a good practice. In a nutshell, would you
> rather use
>
> #+begin_src ocaml
> let x = 12;;
> print_endline "Hello World!"
> #+end_src
>
> or
>
> #+begin_src ocaml
> let x = 12
> let () = print_endline "Hello World!"
> #+end_src
>
> when teaching Ocaml?
>
> Thanks,
>
> Alan
>
> --
> OpenPGP Key ID : 040D0A3B4ED2E5C7
> Weekly CO₂ average (2015-05-30, Mauna Loa Observatory): 403.41 ppm
>
[-- Attachment #2: Type: text/html, Size: 1982 bytes --]
next prev parent reply other threads:[~2015-06-22 13:52 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 [this message]
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
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='CALdWJ+w747WWwKL6KHu-tjpXWKNzR8Jw5Bx3vNvQ-Ux=E=pfkg@mail.gmail.com' \
--to=ivg@ieee.org \
--cc=alan.schmitt@polytechnique.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