From: Therese.Hardin@lip6.fr
To: caml-list@inria.fr
Subject: Curriculum in computer science
Date: Tue, 6 Feb 2001 16:17:16 +0100 (CET) [thread overview]
Message-ID: <14976.5500.318290.821318@meije.lip6.fr> (raw)
We have received the following message from Matthias. We think that it
is relevant to our community, since it concerns particularly
programming languages teaching, but in the long run, the entire
programming activity area.
All the best
Therese Hardin and Pierre Weis
---------------------------------------------
Dear Colleagues
ACM's and IEEE's joint task on curriculum development has released its
"ironman draft" proposal for a new core curriculum in computer science. The
draft allocates six hours to the area of programming languages, relegating
it to third-class status. I have written a letter of protest and ask for
your support. Please visit my Web site where I have posted the letter and
where you can find some additional information on the topic:
http://www.cs.rice.edu/~matthias/cc2001.html
Regards -- Matthias Felleisen
---------------------------------------------
reply other threads:[~2001-02-06 16:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=14976.5500.318290.821318@meije.lip6.fr \
--to=therese.hardin@lip6.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