From: "Yann Régis-Gianas" <yrg@irif.fr>
To: Robert Muller <robert.muller2@gmail.com>
Cc: Ocaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] Recommended teaching setups?
Date: Tue, 30 Oct 2018 07:15:21 +0100 [thread overview]
Message-ID: <CAM+Uc3V0Ct3OK5GbtDGSx1-SEUDATNevtAUqgRAN5XjvJD36Zw@mail.gmail.com> (raw)
In-Reply-To: <CAKmYinnEwLj_KV8SJhkYAd-RR9qGVJT7PsWh5yfUO6PS_L51Ug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1207 bytes --]
Hi Robert,
the subject of your email refers to "teaching" so just to be sure, are you
looking for an environment to teach OCaml? In that case, can you describe
the profile of your students? I am convinced that there is not a single
answer to this question depending on the background of your students.
Cheers,
Le mar. 30 oct. 2018 à 01:31, Robert Muller <robert.muller2@gmail.com> a
écrit :
> Greetings. I've been using OCaml in my programming languages course for
> many years. But I haven't been keeping up with best practices vis-a-vis a
> common environment for unix (MacOS) and Windows users. I've been using
> Vagrant/Virtual Box, with atom + merlin and make files. (Merlin is
> fantastic.) I believe that I should upgrade the build system to use Dune,
> but I'm not sure about the rest of it. If you know of other aspects of this
> setup that I should upgrade, I'd appreciate the heads up.
> Thanks,
> Bob Muller
>
> --
Yann Régis-Gianas
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list https://inbox.ocaml.org/caml-list
Forum: https://discuss.ocaml.org/
Bug reports: http://caml.inria.fr/bin/caml-bugs
[-- Attachment #2: Type: text/html, Size: 1432 bytes --]
next prev parent reply other threads:[~2018-10-30 6:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 0:31 Robert Muller
2018-10-30 6:15 ` Yann Régis-Gianas [this message]
2018-10-30 10:39 ` Robert Muller
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=CAM+Uc3V0Ct3OK5GbtDGSx1-SEUDATNevtAUqgRAN5XjvJD36Zw@mail.gmail.com \
--to=yrg@irif.fr \
--cc=caml-list@inria.fr \
--cc=robert.muller2@gmail.com \
/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).