Effective quotation

Cheney, James; Lindley, Sam; Radanne, Gabriel; Wadler, Philip

doi:10.1145/2543728.2543738

Cited by 8 publications

(4 citation statements)

References 39 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…To make this work we create a second version of every function which handles lineage. This is similar to the doubling translation used by Cheney et al [2014b] to compile a simplified form of L to a F#-like core language. Both translations introduce space overhead and overhead for normal function calls due to pair projections.…”

Section: Dbnmentioning

confidence: 85%

Language-integrated provenance

Fehrenbach

Cheney

2018

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

When referring to this work, full bibliographic details including the author, title, awarding institution and date of the thesis must be given.My thanks, first and foremost, to my advisor James Cheney for his generous guidance, encouragement, and unyielding support. I have left every single one of our meetings happier and more confident than I entered it, even and especially when things had gone poorly. I would also like to thank Peter Buneman, Ian Stark, James McKinna, and Jan Stolarek for their interest and feedback. I would like to thank Torsten Grust and Sam Lindley for agreeing to be my examiners and their feedback, and Stephen Gilmore for chairing my viva.Thanks to my awesome office mates Karoliina, Fabian, Ricardo, and Rudi; to the Friday lunch crowd Brian,

show abstract

Section: Dbnmentioning

confidence: 85%

Language-integrated provenance

Fehrenbach

Cheney

2018

Science of Computer Programming

Self Cite

View full text Add to dashboard Cite

show abstract

“…In [15], Payet et al define operational semantics for a subset of Dalvik opcodes that present registers manipulation, arithmetic operations, object creation, access and method calls as well as Android activities. Semantics rules were relatively complex.…”

Section: Related Workmentioning

confidence: 99%

Smali+: An Operational Semantics for Low-Level Code Generated from Reverse Engineering Android Applications

et al. 2020

View full text Add to dashboard Cite

Today, Android accounts for more than 80% of the global market share. Such a high rate makes Android applications an important topic that raises serious questions about its security, privacy, misbehavior and correctness. Application code analysis is obviously the most appropriate and natural means to address these issues. However, no analysis could be led with confidence in the absence of a solid formal foundation. In this paper, we propose a full-fledged formal approach to build the operational semantics of a given Android application by reverse-engineering its assembler-type code, called Smali. We call the new formal language Smali + . Its semantics consist of two parts. The first one models a single-threaded program, in which a set of main instructions is presented. The second one presents the semantics of a multi-threaded program which is an important feature in Android that has been glossed over in the-state-of-the-art works. All multi-threading essentials such as scheduling, threads communication and synchronization are considered in these semantics. The resulting semantics, forming Smali + , are intended to provide a formal basis for developing security enforcement, analysis and misbehaving detection techniques for Android applications.

show abstract

“…Communications are symmetric and completely dynamic through the use of AJAX. Client-server slicing is dynamic (although some progress has been made towards static query slicing [Cheney et al 2014]) and can introduce "code motion", which can moves closures from the server to the client. This can be extremely problematic in practice, both from an efficiency and a security point of view.…”

Section: Locationsmentioning

confidence: 99%

Eliom: A Core ML Language for Tierless Web Programming

Radanne

Vouillon

Balat

2016

Programming Languages and Systems

Self Cite

View full text Add to dashboard Cite

Tierless Web programming languages allow programmers to combine client-side and server-side programming in a single program. Programmers can then define components with both client and server parts and get flexible, efficient and typesafe client-server communications. However, the expressive client-server features found in most tierless languages are not necessarily compatible with functionalities found in many mainstream languages. In particular, we would like to benefit from type safety, an efficient execution, static compilation, modularity and separate compilation.In this paper, we propose E , an industrial-strength tierless functional Web programming language which extends OC with support for rich client/server interactions. It allows to build whole applications as a single distributed program, in which it is possible to define modular tierless libraries with both server and client behaviors and combine them effortlessly. E is the only language that combines type-safe and efficient client/server communications with a static compilation model that supports separate compilation and modularity. It also supports excellent integration with OC , allowing to transparently leverage its ecosystem.To achieve all these features, E borrows ideas not only from distributed programming languages, but also from meta-programming and modern module systems. We present the design of E , how it can be used in practice and its formalization; including its type system, semantics and compilation scheme. We show that this compilation scheme preserves typing and semantics, and that it supports separate compilation.This juggling of many different technologies does not only make programming more complicated, it also imposes strong constraints on code organization and prevents modularity. Let us consider the case where we want to add a comment widget to a website. This widget requires J S code for client interactions, for example a convenient editor. It also requires server code that will store and serve the comments and potentially some associated database queries. This code will thus be split in two codebases and up to three languages. Furthermore, in order to be properly integrated in the larger website, the internal communications between the client and server parts of the widget will be exposed to the rest of the program. All these programming constraints, which stem directly from the way Web programming is done currently, make it impossible to preserve abstraction and encapsulation for widgets who have both client and server aspects. This hinders safety and reusability of widgets by preventing programmers to create selfcontained independent libraries that have both client and server aspects.: A Language for Modular Tierless Web Programming :3programming often relies on numerous external libraries (for encryption, HTML, logging, . . . ). We wanted to leverage all the existing tools and libraries developed either in the O project or the larger OC ecosystem. The design of a Modular Tierless languageTo build such a language with suppo...

show abstract

Effective quotation

Cited by 8 publications

References 39 publications

Language-integrated provenance

Language-integrated provenance

Smali+: An Operational Semantics for Low-Level Code Generated from Reverse Engineering Android Applications

Eliom: A Core ML Language for Tierless Web Programming

Contact Info

Product

Resources

About