The Research Papers track features presentations from authors of papers accepted at the upcoming The Art, Science, and Engineering of Programming journal. Interested authors should submit their papers to that journal, and choose this year’s Program Chair (Guido Salvaneschi) as the handling editor for their papers.
In order to present at ‹Programming› 2018, papers must be submitted to the first, second or third 2018 issue of that journal (timeline).
Wed 11 AprDisplayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
10:30 - 12:00
|Scoped Extension Methods in Dynamically-Typed Languages|
Research PapersLink to publication DOI
|Towards Zero-Overhead Disambiguation of Deep Priority Conflicts|
Luis Eduardo de Souza Amorim Delft University of Technology, Netherlands, Michael J. Steindorfer Delft University of Technology, Eelco Visser Delft University of TechnologyLink to publication DOI
|Language-integrated provenance in Haskell|
Research PapersLink to publication DOI
13:45 - 15:00
|Lisp, Jazz, Aikido – Three Expressions of a Single Essence|
Didier Verna EPITA / LRDELink to publication DOI
|Live Multi-language Development and Runtime Environments|
Fabio Niephaus Hasso Plattner Institute, University of Potsdam, Tim Felgentreff Oracle Labs, Potsdam, Tobias Pape HPI, Germany, Robert Hirschfeld HPI, University of Potsdam, Marcel Taeumel Hasso Plattner InstituteLink to publication DOI
15:30 - 17:00
|Search-based Tier Assignment for Optimising Offline Availability in Multi-tier Web Applications|
Laure Philips Software Languages Lab, Joeri De Koster Vrije Universiteit Brussel, Belgium, Wolfgang De Meuter Vrije Universiteit Brussel, Coen De Roover Vrije Universiteit BrusselLink to publication DOI
|On the Effect of Semantically Enriched Context Models on Software Modularization|
Amir Saeidi Universiteit Utrecht, Jurriaan Hage Utrecht University, Ravi Khadka Universiteit Utrecht, Slinger JansenLink to publication DOI
|Harmonizing Signals and Events with a Lightweight Extension to Java|
Research PapersLink to publication DOI
Thu 12 AprDisplayed time zone: Amsterdam, Berlin, Bern, Rome, Stockholm, Vienna change
10:30 - 12:00
|Fast, Flexible, Polyglot Instrumentation Support for Debuggers and other Tools|
Michael Van De Vanter Oracle Labs, Chris Seaton Oracle Labs, Michael Haupt eBay, Christian Humer Oracle Labs, Switzerland, Thomas Wuerthinger Oracle LabsLink to publication DOI
|Proactive Empirical Assessment of New Language Feature Adoption via Automated Refactoring: The Case of Java 8 Default Methods|
Raffi Khatchadourian City University of New York (CUNY) Hunter College, Hidehiko Masuhara Tokyo Institute of TechnologyLink to publication DOI
|Introspection for C and its Applications to Library Robustness|
Manuel Rigger Johannes Kepler University Linz, Rene Mayrhofer Johannes Kepler University Linz, Roland Schatz Johannes Kepler University Linz, Matthias Grimmer Oracle Labs, Austria, Hanspeter Mössenböck JKU Linz, AustriaLink to publication DOI Media Attached
13:45 - 15:00
|What we talk about when we talk about monads|
Tomas Petricek Alan Turing InstituteLink to publication DOI
|Deadlock-Free Typestate-Oriented Programming|
Luca Padovani University of Turin, ItalyLink to publication DOI
15:30 - 16:30
|PIE: A Domain-Specific Language for Interactive Software Development Pipelines|
Gabriël Konat Delft University of Technology, Michael J. Steindorfer Delft University of Technology, Sebastian Erdweg TU Delft, Eelco Visser Delft University of TechnologyLink to publication DOI
|Description Languages for Consistency Management Scenarios Based on Examples from the Industry Automation Domain|
Anthony Anjorin , Enes Yigitbas University of Paderborn, Germany, Erhan Leblebici TU Darmstadt, Andy Schürr TU Darmstadt, Marius Lauder Continental Automotive GmbH, Germany, Germany, Martin Witte Siemens AG, GermanyLink to publication DOI
Call for Papers
The Art, Science, and Engineering of Programming accepts papers that advance knowledge of programming. Almost anything about programming is in scope, but in each case there should be a clear relevance to the act and experience of programming. Additionally, papers must be written in a scholarly form. Scholarly works are those that describe ideas in the context of other ideas that are already known, so to contribute to the systematic and long-standing chaining of knowledge. Papers that fail to properly contextualize the work will not be considered.
We accept descriptions of work under different perspectives:
Art: knowledge and technical skills acquired through practice and personal experiences. Examples include libraries, frameworks, languages, APIs, programming models and styles, programming pearls, and essays about programming.
Science (Theoretical): knowledge and technical skills acquired through mathematical formalisms. Examples include formal programming models and proofs.
Science (Empirical): knowledge and technical skills acquired through experiments and systematic observations. Examples include user studies and programming-related data mining.
Engineering: knowledge and technical skills acquired through designing and building large systems and through calculated application of principles in building those systems. Examples include measurements of artifacts’ properties, development processes and tools, and quality assurance methods.
Essays reflecting on topics closely related to programming are likewise welcome.
Independent of the type of work, ‹Programming› accepts submissions covering several areas of expertise, including but not limited to:
- General-purpose programming
- Distributed systems programming
- Parallel and multi-core programming
- Graphics and GPU programming
- Security programming
- User interface programming
- Database programming
- Visual and live programming
- Data mining and machine learning programming, and for programming
- Interpreters, virtual machines, and compilers
- Modularity and separation of concerns
- Model-based development
- Metaprogramming and reflection
- Testing and debugging
- Program verification
- Programming education
- Programming environments
- Social coding
Upon submission, authors are requested to state what type of paper they are submitting and what areas of expertise are covered by the paper. These two classifications, combined, are used to select reviewers and to apply suitable assessment criteria for the papers. They are not used beyond that purpose. Misclassification by the authors may lead to negative assessments from reviewers.
The following criteria are used when evaluating submitted papers:
- Novelty and Importance: The paper presents new insights or results, and contributes significantly to the advancement, analysis, or synthesis of knowledge in the field.
- Scholarship and Clarity: The paper places its ideas and results appropriately and clearly within the context established by previous research in the field.
More specific criteria for assessing papers depends on the type of the paper:
Papers submitted as “The Art” should include a very solid contextualization of the work, and, when applicable, they should include the artifacts themselves. Papers submitted as “Science” should describe the methods or formalisms in detail, as well as any data and scripts used to analyze it. Papers submitted as “Engineering” should present the methods in detail, unveil results that are clearly better than some accepted baseline, and include the artifacts used to reach the conclusions.
Artifacts are recommended, but not required, for the initial submission. Depending on the papers, reviewers may take the existence of artifacts as a positive signal about the work. Also depending on the papers, artifacts may be required as a condition for publication.
There are two rounds of review. The first round assesses the papers according to the quality criteria stated above, and results in the selection of a subset of submissions that are either accepted as-is or are deemed potentially acceptable. All other papers are rejected. Authors of potentially acceptable papers are requested to improve specific aspects of the research and the paper. Authors are given a specified period of time to perform the revisions and re-submit the paper. During the second and final reviewing round, the same reviewers assess how well the revision requests have been addressed by the authors, and whether the final paper maintains or improves the level of contribution of the original submission. Revisions that significantly lessen the contribution of the work or that fail to adequately address the reviewers’ original concerns will result in the paper’s rejection.
Papers rejected in either the first or second phases may be resubmitted one more time to the journal. The resubmission will be treated as a new submission, and the paper may be assigned to new reviewers. After a second rejection, subsequent submissions of the same paper will be desk-rejected.
Information for Authors
Use the the online submission system at EasyChair.
The template is also available in Overleaf.
Papers must be written in English using high standards of writing. Papers that show poor mastery of the English language will be rejected without review.
The main part of the paper should not exceed 22 pages (in the provided style), but there is no limit for bibliography and appendices. The page limit for the main part of the paper is in place in order to keep the paper on focus and to avoid overloading the reviewers. Authors are encouraged to move important details to appendices, which may be consulted by the reviewers. In some cases, if authors feel that the main part requires substantially more pages, they should explain the reasons why in the additional comments field of the submission form; examples of these cases may include papers with substantial source code listings, and essays. Papers whose length is incommensurate with their contribution will be rejected.
The submission is required to contain an ACM subject classification.
Each submission must be accompanied by a plain-language abstract of up to 500 words that presents the key points in the paper in a manner understandable by experienced practitioners and researchers in nearby disciplines. The abstract should avoid mathematical symbols whenever possible, and it must address the following:
- Context: What is the broad context of the work? What is the importance of the general research area?
- Inquiry: What problem or question does the paper address? How has this problem or question been addressed by others (if at all)?
- Approach: What was done that unveiled new knowledge?
- Knowledge: What new facts were uncovered? If the research was not results oriented, what new capabilities are enabled by the work?
- Grounding: What argument, feasibility proof, artifacts, or results and evaluation support this work?
- Importance: Why does this work matter?
NOTE: The absence of an abstract conforming to this specification is grounds for the rejection of the paper without review.
Submitted papers must present original work made by the authors, must not overlap significantly with the authors’ previously published work, and must not be under review on another journal or conference.