caml-list - the Caml user's mailing list
 help / Atom feed
From: Gidon Ernst <gidon.ernst@unimelb.edu.au>
To: "caml-list@inria.fr" <caml-list@inria.fr>
Subject: [Caml-list] FTfJP 2019: Call for Papers
Date: Thu, 14 Mar 2019 00:33:17 +0000
Message-ID: <ef18f5b1-af2d-33a1-85c1-00ff49055e1d@unimelb.edu.au> (raw)

# CALL FOR PAPERS

21st Workshop on Formal Techniques for Java-like Programs (FTfJP 2019)
https://conf.researchr.org/home/FTfJP-2019/

Co-located with ECOOP 2019, July 15-19, Hammersmith, London

## About FTfJP 2019
Formal techniques can help analyse programs, precisely describe
program behaviour, and verify program properties. Modern programming
languages are interesting targets for formal techniques due to their
ubiquity and wide user base, stable and well-defined interfaces and
platforms, and powerful (but also complex) libraries. New languages
and applications in this space are continually arising, resulting in
new programming languages (PL) research challenges.

Work on formal techniques and tools and on the formal underpinnings of
programming languages themselves naturally complement each
other. FTfJP is an established workshop which has run annually since
1999 alongside ECOOP, with the goal of bringing together people
working in both fields.

The workshop has a broad PL theme; the most important criterion is
that submissions will generate interesting discussions within this
community. The term “Java-like” is somewhat historic and should be
interpreted broadly: FTfJP solicits and welcomes submission relating
to programming languages in general, beyond Java, C#, Scala, etc.

Example topics of interest include:

* Language design and semantics
* Type systems
* Concurrency and new application domains
* Specification and verification of program properties
* Program analysis (static or dynamic)
* Program Synthesis
* Security
* Pearls (programs or proofs)

FTfJP welcomes submissions on technical contributions, case studies,
experience reports, challenge proposals, and position papers.


## Submissions

Contributions are sought in two categories:

* Full Papers (6 pages, excluding references) present a technical
  contribution, case study, or detailed experience report. We welcome
  both complete and incomplete technical results; ongoing work is
  particularly welcome, provided it is substantial enough to stimulate
  interesting discussions.

* Short Papers (2 pages, excluding references) should advocate a
  promising research direction, or otherwise present a position likely
  to stimulate discussion at the workshop. We encourage
  e.g. established researchers to set out a personal vision, and
  beginning researchers to present a planned path to a PhD.

Both types of contributions will benefit from feedback received at the
workshop. Submissions will be peer reviewed, and will be evaluated
based on their clarity and their potential to generate interesting
discussions. The format of the workshop encourages interaction. FTfJP
is a forum in which a wide range of people share their expertise, from
experienced researchers to beginning PhD students.


## Formatting and Publication

Submissions should be in acmart/sigplan style, 10pt font. Formatting
requirements are detailed on the SIGPLAN Author Information page
(https://www.sigplan.org/Resources/Author).

Accepted papers will be published in the ACM Digital Library by
default, though authors will be able to opt out of this publication,
if desired. At least one author of an accepted paper must attend the
workshop to present the work and participate in the discussions.


## Important Dates

* Submission: 21 April (AoE)
* Notification: 2 June


## Program Committee

* Yuyan Bao (Pennsylvania State University)
* James Bornholt (University of Washington)
* Gidon Ernst (Co-Chair; LMU Munich)
* Marie Farrell (University of Liverpool)
* Carlo A. Furia (USI – Università della Svizzera Italiana)
* Marie-Christine Jakobs (TU Darmstadt)
* Wojciech Mostowski (Halmstad University)
* Toby Murray (Co-Chair; University of Melbourne)
* Christine Rizkallah (University of New South Wales and Data61)
* Martin Schäf (Amazon Web Services)




                 reply index

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publically 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=ef18f5b1-af2d-33a1-85c1-00ff49055e1d@unimelb.edu.au \
    --to=gidon.ernst@unimelb.edu.au \
    --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

caml-list - the Caml user's mailing list

Archives are clonable: git clone --mirror https://inbox.ocaml.org/caml-list

AGPL code for this site: git clone https://public-inbox.org/ public-inbox