From: Ekaterina Komendantskaya <komendantskaya@gmail.com>
To: Katya Komendantskaya <komendantskaya@gmail.com>
Subject: [Caml-list] PPDP'19 Final CFP
Date: Fri, 12 Apr 2019 11:29:49 +0100 [thread overview]
Message-ID: <CAEQEJxL+deTrKBwJviWmQJQ1mmw8MorCmkgSpuVfjSwvh1ACzQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2710 bytes --]
FINAL CALL FOR PAPERS -- PPDP 2019
21st International Symposium on
Principles and Practice of Declarative Programming
7–9 October 2019, Porto, Portugal
Collocated with FM'19
http://ppdp2019.macs.hw.ac.uk
======================================================================
Important Dates
---------------
Title and abstract registration 26 April 2019 (AoE)
Paper submission 3 May 2019 (AoE)
Rebuttal period (48 hours) 3 June 2019 (AoE)
Author notification 14 June 2019
Final paper version 15 July 2019
Conference 7–9 October 2019
About PPDP
----------
The PPDP 2019 symposium brings together researchers from the declarative
programming communities, including those working in the functional, logic,
answer-set, and constraint handling programming paradigms. The goal is to
stimulate research in the use of logical formalisms and methods for
analyzing,
performing, specifying, and reasoning about computations, including
mechanisms
for concurrency, security, static analysis, and verification.
Invited Speakers
----------------
Amal Ahmed Northeastern University, USA
Title: TBA
Naoki Kobayashi The University of Tokyo, Japan
Title: 10 Years of the Higher-Order Model Checking Project
Scope
-----
Submissions are invited on all topics related to declarative programming,
from
principles to practice, from foundations to applications. Topics of
interest
include, but are not limited to
- Language Design: domain-specific languages; interoperability;
concurrency,
parallelism and distribution; modules; probabilistic languages; functional
languages; reactive languages; database languages; knowledge representation
languages; languages with objects; language extensions for tabulation;
metaprogramming.
- Implementations: abstract machines; interpreters; compilation;
compile-time
and run-time optimization; memory management.
- Foundations: types; logical frameworks; monads and effects; semantics.
- Analysis and Transformation: partial evaluation; abstract interpretation;
control flow; data flow; information flow; termination analysis; resource
analysis; type inference and type checking; verification; validation;
debugging; testing.
- Tools and Applications: programming and proof environments; verification
tools; case studies in proof assistants or interactive theorem provers;
certification; novel applications of declarative programming inside and
outside of CS; declarative programming pearls; practical experience reports
and industrial application; education.
For further information, please visit:
http://ppdp2019.macs.hw.ac.uk
[-- Attachment #2: Type: text/html, Size: 20183 bytes --]
next reply other threads:[~2019-04-12 10:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-12 10:29 Ekaterina Komendantskaya [this message]
2019-04-12 11:59 ` Gabriel Scherer
2019-04-12 12:30 ` Ekaterina Komendantskaya
2019-04-12 14:16 ` Gabriel Scherer
2019-04-18 9:36 ` Ekaterina Komendantskaya
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=CAEQEJxL+deTrKBwJviWmQJQ1mmw8MorCmkgSpuVfjSwvh1ACzQ@mail.gmail.com \
--to=komendantskaya@gmail.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).