From: Kwangkeun Yi <kwang@ropas.snu.ac.kr>
To: caml-list@inria.fr
Subject: [Caml-list] How to shape our [SW construction] course?
Date: Wed, 20 Mar 2013 18:23:05 +0900 [thread overview]
Message-ID: <51497FF9.1070102@ropas.snu.ac.kr> (raw)
Hi OCamlers,
We at Seoul National University are changing our programming curricula
so that junior CS students will be trained to build rather big
softwares. After some discussions we decided to use C++ :-(
Is there any good idea on nudging(or even forcing) programming in C++
become more like programming in OCaml? I want our students to enjoy the
merits of high-level, higher-order & typed programming language in this
class even in C++. Would it be possible?
Maybe I need to build some layer of libraries...
I'd like to hear, if any, more interesting ideas or your experience in
this context.
All the best,
-Kwang
--
Prof. Kwangkeun Yi
Computer Science & Engineering
Seoul National University
http://ropas.snu.ac.kr/~kwang
next reply other threads:[~2013-03-20 9:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 9:23 Kwangkeun Yi [this message]
2013-03-20 14:07 ` Edgar Friendly
2013-03-20 17:39 ` Ashish Agarwal
[not found] <fa.O+GZy4Ef86RPjYk+BRq3j/diyUQ@ifi.uio.no>
2013-03-22 22:46 ` pulmu
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=51497FF9.1070102@ropas.snu.ac.kr \
--to=kwang@ropas.snu.ac.kr \
--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).