From: Kathleen Fisher <kfisher@research.att.com>
To: erlang-questions@erlang.org, haskell@haskell.org,
plt-scheme@slow.flux.utah.edu, caml-list@yquem.inria.fr,
MLton-user@mlton.org
Subject: CUFP Final Program and Early Registration Deadline Reminder
Date: Tue, 15 Aug 2006 23:14:41 -0700 [thread overview]
Message-ID: <45F212A5-A643-4F89-9E8D-4F8F01C228DF@research.att.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1513 bytes --]
Hi all!
Reminder! The early registration deadline for Commercial Users of
Functional Programing (CUFP) is this Friday, August 18.
Registration is available from the ICFP registration page:
http://regmaster2.com/conf/icfp2006.html
CUFP will take place on Thursday, September 21st, the day after ICFP.
The final program for CUFP is now available:
8:30 Haskell and the Linspire Toolchain.
Clifford Beshers, Linspire Inc.
9:00 Automated Testing of Reactive Systems with SML.
Steve Sims, Reactive Systems, Inc.
9:30 Scheme in Space.
Richard Cleis, Air Force Research Lab.
10:00 B R E A K
10:30 Mission Critical OCaml: Experiences using FP in Finance.
Yaron Minsky, Jane Street Capital. abstract
11:00 Why Functional Programming Matters to Credit Suisse.
Gabriele Keller and Lennart Augustsson, Credit Suisse First
Boston. abstract
11:30 Group Discussion: Mixed Mode Approaches and/or Finding Employees.
12:00 L U N C H
2:00 Analysis of Microprocessor Components with a Functional
Language-based Formal Verification Toolbox.
Roope Kaivola, Intel Corporation.
2:30 Teaching Old Dogs New Tricks: Selling Bluespec to Hardware
Designers.
Rishiyir Nihkil, Bluespec, Inc.
3:00 Group Discussion: Adoption of New Technology: Making the Case.
3:30 B R E A K
4:00 Artifically Intelligent Haskell.
J. Garret Morris, Aetion Inc.
4:30 Betting on Functional Programming and Winning.
Erik Stenman, Kreditor.
5:00 Wrap-Up.
[-- Attachment #2: Type: text/html, Size: 4072 bytes --]
reply other threads:[~2006-08-16 6:14 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=45F212A5-A643-4F89-9E8D-4F8F01C228DF@research.att.com \
--to=kfisher@research.att.com \
--cc=MLton-user@mlton.org \
--cc=caml-list@yquem.inria.fr \
--cc=erlang-questions@erlang.org \
--cc=haskell@haskell.org \
--cc=plt-scheme@slow.flux.utah.edu \
/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).