Demonstration venue · read-only. Every page can be browsed; the buttons that would change it are switched off. Create an account to run TaxoReview on your own data. A simulation from public publication records: the people listed were not invited and did not agree to review.
? Tutorial for this page

Johan Östlund

dblp:32/5778 · DBLP profile ↗
← Back
4ranked-venue papers
1as first author
0since 2021 · last 2012
—ORCID · none

Domains — the database's venue-derived domains; a paper can count in several

Software engineering, systems software and programming languages · 4 · 1 first-author

Expertise — from the expertise taxonomy: the topics of the expert's papers under the CCF categories. A weight counts papers with recency: 1 for a paper about the topic, 0.3 when the topic is its context, halved every five years.

Software engineering, system software, and programming languages
2 papers
Programming languages and type systems · 81% Concurrent programming · 15% Runtime systems and virtual machines · 4%

Topics — the 6 heaviest of 7, each with the papers that count most for it

TopicWeightPapersLastEvidence papers
Programming languages and type systems › type systems
dynamic typing
0.112010
Integrating typed and untyped code in a scripting language · POPL 2010
Programming languages and type systems › type systems
gradual typing
0.112010
Integrating typed and untyped code in a scripting language · POPL 2010
Programming languages and type systems › type systems
static typing
0.112010
Integrating typed and untyped code in a scripting language · POPL 2010
Programming languages and type systems
language design
0.112009
Thorn: robust, concurrent, extensible scripting on the JVM · OOPSLA 2009
Concurrent programming
message passing
0.112009
Thorn: robust, concurrent, extensible scripting on the JVM · OOPSLA 2009
Programming languages and type systems
type systems
0.112009
Thorn: robust, concurrent, extensible scripting on the JVM · OOPSLA 2009

Methods — techniques the papers use, named apart from their topics

type checking · 0.1operational semantics · 0.1compiler plugin mechanism · 0.1
YearPublicationVenuePosition
2012 Multiple Aggregate Entry Points for Ownership Types
Johan Östlund, Tobias Wrigstad
ECOOP1
2010 Integrating typed and untyped code in a scripting language
abstract
Many large software systems originate from untyped scripting language code. While good for initial development, the lack of static type annotations can impact code-quality and performance in the long run. We present an approach for integrating untyped code and typed code in the same system to allow an initial prototype to smoothly evolve into an efficient and robust program. We introduce like types , a novel intermediate point between dynamic and static typing. Occurrences of like types variables are checked statically within their scope but, as they may be bound to dynamic values, their usage is checked dynamically. Thus like types provide some of the benefits of static typing without decreasing the expressiveness of the language. We provide a formal account of like types in a core object calculus and evaluate their applicability in the context of a new scripting language.
Tobias Wrigstad, Francesco Zappa Nardelli, Sylvain Lebresne, Johan Östlund, Jan Vitek
POPL4
2009 Thorn: robust, concurrent, extensible scripting on the JVM
abstract
Scripting languages enjoy great popularity due to their support for rapid and exploratory development. They typically have lightweight syntax, weak data privacy, dynamic typing, powerful aggregate data types, and allow execution of the completed parts of incomplete programs. The price of these features comes later in the software life cycle. Scripts are hard to evolve and compose, and often slow. An additional weakness of most scripting languages is lack of support for concurrency - though concurrency is required for scalability and interacting with remote services. This paper reports on the design and implementation of Thorn, a novel programming language targeting the JVM. Our principal contributions are a careful selection of features that support the evolution of scripts into industrial grade programs - e.g., an expressive module system, an optional type annotation facility for declarations, and support for concurrency based on message passing between lightweight, isolated processes. On the implementation side, Thorn has been designed to accommodate the evolution of the language itself through a compiler plugin mechanism and target the Java virtual machine.
Bard Bloom, John Field, Nathaniel Nystrom, Johan Östlund, Gregor Richards, Rok Strnisa, Jan Vitek, Tobias Wrigstad
OOPSLA4
2008 Minimal Ownership for Active Objects
Dave Clarke 0001, Tobias Wrigstad, Johan Östlund, Einar Broch Johnsen
APLAS3