From: ByronHale <byron.hale@einfo.com>
To: Bay Area Functional Programmers <bayfp@googlegroups.com>
Cc: comp-lang-ml@moderators.isc.org, caml-list@yquem.inria.fr,
ocaml_beginners@yahoogroups.com, erlang-questions@erlang.org
Subject: Congratulations on the new SFBA functional programming group: "Bay Area Functional Programmers"
Date: Sun, 04 Nov 2007 02:39:30 -0800 [thread overview]
Message-ID: <1194172770.704442.197090@v23g2000prn.googlegroups.com> (raw)
At various times, some of us in the SFBA have met for OCaml, SML97 and
Erlang. In our last implementation, we struggled to find a congenial
location. It would probably have to be Stanford or Berkeley, due to
the overall poor transportation system in the SFBA. The location at
Stanford with Cal Train shuttle service, is therefore excellent news.
It looks as if there is a critical mass, too!
Best Regards,
Byron Hale
byron.hale@einfo.com
For other lists:
Next meeting:
Wednesday, Nov 7, 7:30 PM
Carnegie Institute on the Stanford campus
reply other threads:[~2007-11-04 10:40 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=1194172770.704442.197090@v23g2000prn.googlegroups.com \
--to=byron.hale@einfo.com \
--cc=bayfp@googlegroups.com \
--cc=caml-list@yquem.inria.fr \
--cc=comp-lang-ml@moderators.isc.org \
--cc=erlang-questions@erlang.org \
--cc=ocaml_beginners@yahoogroups.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).