caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Loup Vaillant" <loup.vaillant@gmail.com>
To: "David Teller" <David.Teller@univ-orleans.fr>
Cc: OCaml <caml-list@inria.fr>
Subject: Re: [Caml-list] Which syntax to teach ?
Date: Wed, 24 Oct 2007 15:18:31 +0200	[thread overview]
Message-ID: <6f9f8f4a0710240618r1f389049n47b303f98ebf620f@mail.gmail.com> (raw)
In-Reply-To: <1193225773.3612.27.camel@Blefuscu>

2007/10/24, David Teller <David.Teller@univ-orleans.fr>:
>    Hello list,
>
> [...] but requires additional command-line arguments to ocamlc


Why not just set up an alias or a little script (and an appropriate
custom toplevel)? That would ease the first lessons. For those who
want to work at home, just tell them the magic formulae. Explanations
can come later.


> not sure I'll be able to find an editor that will display that syntax
> nicely.

The Tuareg mode in emacs colours the revised syntax well. I just don't
know   how to make the embedded toplevel work properly (a trailing
";;;" problem). Maybe someone knows how to tweak it?


>  Any suggestions or experiences ?

A few. But beware: The following is a student's point of view. I don't
know how to teach. I never did.

I first learnt Caml light on its toplevel. While it is a huge helper
for learning, I wasn't told about the compiler. Therefore, I thought
the "Caml system" was closed, and useless as such.

I took two beginner courses in Caml. The first emphasised syntax
first, and the second emphasised semantics first (and actually used
very few syntactic constructs). The latter was faster and more
enjoying.

Some students need a computer at the very first lesson (my brother is
one of them). I hope you can afford it.

The word "powerful" have a semantic load that scares students.
Sentences like "It is easy to do plenty of stuff with little code"
don't.

My two cents.
Loup Vaillant


  reply	other threads:[~2007-10-24 13:18 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-24 11:36 David Teller
2007-10-24 13:18 ` Loup Vaillant [this message]
2007-10-24 13:24 ` [Caml-list] " Peng Zang
2007-10-24 13:54   ` Julien Moutinho
2007-10-24 17:23 ` Andrej Bauer
2007-10-24 19:05   ` Adrien
2007-10-25  5:14     ` Aleks Bromfield
2007-10-30 16:26     ` Chung-chieh Shan
2007-10-30 16:38       ` [Caml-list] " Brian Hurt
2007-10-30 16:59         ` Chung-chieh Shan
2007-10-30 17:08         ` [Caml-list] " Edgar Friendly
2007-10-30 17:56           ` skaller
2007-10-30 19:02             ` Vincent Aravantinos
2007-10-30 18:50           ` William D. Neumann
2007-10-30 21:45           ` Eliot Handelman
2007-10-30 18:56       ` Daniel Bünzli
2007-10-25  9:43   ` [Caml-list] " Richard Jones
2007-10-24 22:52 ` Nathaniel Gray
2007-10-24 23:10   ` Jon Harrop
2007-10-25  1:48     ` skaller
2007-10-25  2:02       ` Jon Harrop
2007-10-25  9:49       ` Richard Jones
2007-10-25 11:32         ` Stefano Zacchiroli
2007-10-25 11:52           ` Daniel Bünzli
2007-10-25 12:39           ` Richard Jones
2007-10-25 12:59         ` Michael Ekstrand
2007-10-25 13:39           ` Loup Vaillant
2007-10-25 20:32             ` Andrej Bauer
2007-10-25 22:11               ` Loup Vaillant
2007-10-25 15:14           ` Richard Jones
2007-10-25 18:47             ` Re : " Adrien
2007-11-02 16:08       ` Nathaniel Gray
2007-10-26 11:11     ` David Teller
2007-10-24 23:02 ` Jon Harrop
2007-10-26 11:09   ` David Teller

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=6f9f8f4a0710240618r1f389049n47b303f98ebf620f@mail.gmail.com \
    --to=loup.vaillant@gmail.com \
    --cc=David.Teller@univ-orleans.fr \
    --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;
as well as URLs for NNTP newsgroup(s).