Modules as gradually-typed objects

Homer, Michael; Bruce, Kim B.; Noble, James; Black, Andrew P.

doi:10.1145/2489798.2489799

Cited by 9 publications

(5 citation statements)

References 24 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Dialects can provide new features to the language and new tiles in the toolbox, and impose additional restrictions on what can be written. Each module [7] of the program can use a different dialect. Different dialects can provide drastically different sublanguages, with their own tiles and rules, within the same overall syntax and semantics.…”

Section: Tiled Gracementioning

confidence: 99%

Lessons in combining block-based and textual programming

Homer¹,

Noble²

2017

VLSS

Self Cite

View full text Add to dashboard Cite

Tiled Grace is a block-based programming system backed by a conventional textual language that allows switching back and forth between block-based and textual editing of the same code at any time. We discuss the design choices of Tiled Grace in light of existing research and a user experiment conducted with it. We also examine the sorts of task preferred in each mode by users who had the choice of editing either as blocks or as text, and find both positive and cautionary notes for block-based programming in the results.

show abstract

Section: Tiled Gracementioning

confidence: 99%

Lessons in combining block-based and textual programming

Homer¹,

Noble²

2017

VLSS

Self Cite

View full text Add to dashboard Cite

show abstract

“…Grace is not an dynamically typed language that has been extended with an optional type system, but a language that has been designed from the ground up to have both static and dynamic typing. Homer et al [15] explores some useful patterns that derive from Grace's use of objects as modules and its brand of optional structural typing, which can also be expressed with Typed Lua's modules as tables.…”

Section: Related Workmentioning

confidence: 99%

Typed Lua

Maidl

Mascarenhas

Ierusalimschy

2014

Proceedings of the Workshop on Dynamic Languages and Applications

View full text Add to dashboard Cite

Dynamically typed languages trade flexibility and ease of use for safety, while statically typed languages prioritize the early detection of bugs, and provide a better framework for structure large programs. The idea of optional typing is to combine the two approaches in the same language: the programmer can begin development with dynamic types, and migrate to static types as the program matures. The challenge is designing a type system that feels natural to the programmer that is used to programming in a dynamic language.This paper presents the initial design of Typed Lua, an optionally-typed extension of the Lua scripting language. Lua is an imperative scripting language with first class functions and lightweight metaprogramming mechanisms. The design of Typed Lua's type system has a novel combination of features that preserves some of the idioms that Lua programmers are used to, while bringing static type safety to them. We show how the major features of the type system type these idioms with some examples, and discuss some of the design issues we faced.

show abstract

“…Modules are imported by designating a path to the containing file, and a name to give the module. Modules are also objects, and all top-level public definitions in a file are exposed on the resulting object when the module is imported (Homer, K. B. Bruce, et al 2013). A module runs when it is first imported, and subsequent imports receive a pointer to the existing object.…”

Section: The Core Languagementioning

confidence: 99%

Classless Object Semantics

Jones¹

View full text Add to dashboard Cite

<p>Objects have been categorised into classes that declare and implement their behaviour ever since the paradigm of object-orientation in programming languages was first conceived. Classes have an integral role in the design and theory of object-oriented languages, and often appear alongside objects as a foundational concept of the paradigm in many theoretical models. A number of object-oriented languages have attempted to remove classes as a core component of the language design and rebuild their functionality purely in terms of objects, to varying success. Much of the formal theory of objects that eschews classes as a fundamental construct has difficulty encoding the variety of behaviours possible in programs from class-based languages. This dissertation investigates the foundational nature of the class in the object-oriented paradigm from the perspective of an ‘objects-first’, classless language. Using the design of theoretical models and practical implementations of these designs as extensions of the Grace programming language, we demonstrate how objects can be used to emulate the functionality of classes, and the necessary trade-offs of this approach. We present Graceless, our theory of objects without classes, and use this language to explore what class functionality is difficult to encode using only objects. We consider the role of classes in the types and static analysis of object-oriented languages, and present both a practical design of brand objects and a corresponding extension of our theory that simulates the discipline of nominal typing. We also modify our theory to investigate the semantics of many different kinds of implementation reuse in the form of inheritance between both objects and classes, and compare the consequences of these different approaches.</p>

show abstract

Modules as gradually-typed objects

Cited by 9 publications

References 24 publications

Lessons in combining block-based and textual programming

Lessons in combining block-based and textual programming

Typed Lua

Classless Object Semantics

Contact Info

Product

Resources

About