unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Andy Keep (akeep)" <akeep@cisco.com>
To: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: [CFP] SECOND NOTICE: Scheme and Functional Programming Workshop 2015
Date: Mon, 18 May 2015 04:37:23 +0000	[thread overview]
Message-ID: <etPan.55596c93.7d8d6d74.1712@akeep-M-4063> (raw)

[-- Attachment #1: Type: text/plain, Size: 2637 bytes --]

========================================================================

SECOND NOTICE: DEADLINE THIS FRIDAY!
Call For Papers:

Scheme and Functional Programming Workshop 2015
Vancouver, British Columbia, Canada
(Co-located with ICFP 2015)

http://andykeep.com/SchemeWorkshop2015/

========================================================================

Submissions related to Scheme, Racket, Clojure, and functional
programming are welcome and encouraged. Topics of interest include
but are not limited to:

  * Program-development environments, debugging, testing
  * Implementation (interpreters, compilers, tools, benchmarks, etc.)
  * Syntax, macros, hygiene
  * Distributed computing, concurrency, parallelism
  * Interoperability with other languages, FFIs
  * Continuations, modules, object systems, types
  * Theory, formal semantics, correctness
  * History, evolution and standardization of Scheme
  * Applications, experience and industrial uses of Scheme
  * Education
  * Scheme pearls (elegant, instructive uses of Scheme)

We also welcome submissions related to dynamic or multiparadigmatic
languages and programming techniques.

========================================================================

Important Dates:

May 22nd, 2015 - Paper deadline
June 26th, 2015 - Author notification
July 19th, 2015 - Camera-ready deadline
September 4th, 2015 - Workshop

========================================================================

Submissions must be in ACM proceedings format, no smaller than 9-point
type (10-point type preferred). Microsoft Word and LaTeX templates for
this format are available at:
http://www.acm.org/sigs/sigplan/authorInformation.htm

Submissions should be in PDF and printable on US Letter.

To encourage authors to submit their best work, this year we are
encouraging shorter papers (around 6 pages, excluding references). This
is to allow authors to submit longer, revised versions of their papers
to archival conferences or journals. Longer papers (10--12 pages) are
also acceptable, if the extra space is needed. There is no maximum
length limit on submissions, but good submissions will likely be in the
range of 6 to 12 pages.

More information available at: http://andykeep.com/SchemeWorkshop2015/

========================================================================

Organizers:
Andy Keep, Cisco Systems Inc. (General Chair)
Ryan Culpepper, Northeastern University (Program Chair)

(Apologies for duplications from cross-posting.)

========================================================================

[-- Attachment #2: Type: text/html, Size: 3846 bytes --]

                 reply	other threads:[~2015-05-18  4:37 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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=etPan.55596c93.7d8d6d74.1712@akeep-M-4063 \
    --to=akeep@cisco.com \
    --cc=guile-user@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).