DOCSLIB.ORG

Trait-Oriented Programming in Java 8 Viviana Bono, Enrico Mensa, Marco Naddeo

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Trait-Oriented Programming in Java 8 Viviana Bono, Enrico Mensa, Marco Naddeo Trait-oriented Programming in Java 8 Viviana Bono, Enrico Mensa, Marco Naddeo To cite this version: Viviana Bono, Enrico Mensa, Marco Naddeo. Trait-oriented Programming in Java 8. PPPJ’14: International Conference on Principles and Practices of Programming on the Java Platform: virtual machines, languages, and tools, Sep 2014, Cracow, Poland. hal-01026531 HAL Id: hal-01026531 https://hal.inria.fr/hal-01026531 Submitted on 22 Aug 2014 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Trait-oriented Programming in Java 8 ∗ VivianaBono EnricoMensa MarcoNaddeo Dipartimento di Informatica, University of Torino, Italy {bono,naddeo}@di.unito.it, [email protected] Abstract elements in the collection. However, adding this method as ab- Java 8 was released recently. Along with lambda expressions, a new stract to Collection<T> interface would mean breaking back- language construct is introduced: default methods in interfaces. The ward compatibility: in other words, every old class implementing intent of this feature is to allow interfaces to be extended over Collection<T> interface would have to change by adding an im- time preserving backward compatibility. In this paper, we show plementation of forEach(LE), unless a default method is present a possible, different use of interfaces with default methods: we in the interface. Moreover, default methods may help avoiding code introduce a trait-oriented programming style based on an interface- duplication. as-trait idea, with the aim of improving code modularity. Starting In previous Java releases, interfaces were to provide multiple from the most common operators on traits, we introduce some type inheritance, in contrast to the class-based single implementa- programming patterns mimicking such operators and discuss this tion inheritance. Java 8 interfaces, instead, introduce a form of mul- approach. tiple implementation inheritance, too. Therefore, they are similar to traits [10], which are sets of (required and supplied) methods. 1 Categories and Subject Descriptors D.3.3 [Programming Lan- Java 8 interfaces, then, can be exploited to introduce a trait-oriented guages]: Language Constructs and Features programming style. Note that we are not proposing a linguistic ex- tension of Java 8 with traits, but programming patterns within Java Keywords Java 8, default method, trait, programming pattern, 8, with the goal of improving code modularity and, therefore, code code modularity. reuse. Starting from operators on traits [10], we introduce some Java 8 programming patterns mimicking such operators and dis- 1. Introduction cuss this approach. From the point of view of the language constructs, the most promi- The paper is organized as follows: Section 2 illustrates briefly nent addition in Java 8 is the lambda-expression construct, that the trait construct, Section 3 introduces Java 8 default methods, comes along with an apparently secondary construct, that is, the de- Section 4 proposes the programming patterns inspired by the trait fault method (aka virtual extension method, aka defender method) operators, Section 5 shows an example of use, Section 6 makes in interfaces. The primary intent of this feature is to allow interfaces some comparisons with related work, and Section 7 draws some to be extended over time preserving backward compatibility. These conclusions. features of Java 8 are described in the proposal JEP 126 (JDK En- hancement Proposal 126) Lambda Expressions & Virtual Exten- 2. What are traits? sions Methods [9]. JEP 126 is a follower of the Project Lambda, that corresponds to JSR 335 (Java Specification Request 335) [17]. The possibility of composition and decomposition of code are im- A default method is a virtual method that specifies a con- portant characteristics to care about in a programming language. crete implementation within an interface: if any class implement- Let us point out some problems of (single and multiple) inheritance ing the interface will override the method, the more specific im- concerning composability: plementation will be executed. But if the default method is not • Duplicated features. Single inheritance is the basic form of in- overridden, then the default implementation in the interface will heritance; thanks to that we can reuse a whole class (and also be executed. An already paradigmatic example of use of de- add some features). But sometimes we want to express some- fault methods to preserve backward compatibility concerns the thing that is much too complex to be implemented with single interface Collection<T>, already present in previous releases inheritance. For example, we could have a class Swimming (that of Java. Thanks to lambda expressions, now it is possible to in- gives features for swimming animals) and a class Flying (that troduce a forEach(LE) method that takes a lambda expression gives features for flying animals). What if we want to create an LE as an argument, coding a function to be applied to all of the animal that can both swim and fly, as swans? We can inherit ∗ only from Swimming or Flying but not both, so we will have This material is based upon work supported by MIUR PRIN Project CINA to duplicate some of the existing features in the Swan class. Prot. 2010LHT4KM and Ateneo/CSP Project SALT. • Inappropriate hierarchies. Instead of duplicating methods in the lower classes, we can bring those methods up in the hier- archy; however, this way we violate the semantics of the upper classes. • Conflicting features. If we have multiple inheritance (as C++ does) a common problem is how to treat conflicts. Method conflicts can be solved (for example, thanks to overriding), but [Copyright notice will appear here once ’preprint’ option is removed.] 1 This is pointed out in many places, see, for instance, [18]. 1 2014/7/22 conflicting attributes are more problematic. It is never clear if a 3. On default methods conflicting attribute should be inherited once or twice and how The role of an interface up to Java 7 was to give a contract to the these attributes should be initialized. user (that is, a type), but not to specify any detail of the contract it- self (that is, the implementation). The main characteristic of default Traits are a possible solution to these problems. A trait is a “simple methods (introduced by a keyword ) is that they are virtual conceptual model for structuring object-oriented programs” [10] default like all methods in Java, but they provide a default implementation and it is a collection of methods. This is very important: these traits within an interface. are statless, they cointain only methods, therefore every conflict of Java 8 method resolution is defined in [12] and its formalization state is avoided. Only method name conflicts must be dealt with, in a Featherweight-Java style [14] can be found in [13]. To summa- explicitly, by the programmer. rize it, we take the four (informal) rules about method linkage from Every trait can define required methods and required fields. In [13]: the considered model, required fields are indirectly modelled via required setter and getter methods. A trait can be defined directly • A method defined in a type takes precedence over methods (by specifying its methods) or by composing one or more traits. The defined in its supertypes. composition is performed by means of the following operators: • A method declaration (concrete or abstract) inherited from a • Symmetric Sum: a new trait is defined by combining two or superclass takes precedence over a default inherited from an more existing traits whose method sets are disjoint. In the case interface. the sets are not disjoint, conflicts arise. • More specific default-providing interfaces take precedence over • Trait overriding: a new trait is defined by adding method(s) to less specific ones. an existing trait. If an already present method is added, the old • Ifweareto link m() to a default method from an interface, there version is overridden. must be a unique most specific default-providing interface to • Exclusion: a new trait is defined by excluding a method from an link to, otherwise the compiler signals a conflict. existing trait. From these dispatch rules, we can extrapolate some examples of • Aliasing: a new trait is defined by adding a second name to a behaviour that can help the reader to understand the default method method from an existing trait. This is useful if the original name construct. was excluded after resolving a conflict. Note that, if a recursive A first example. If the class that implements the interface using method is aliased, the recursive call will be done on the original default methods does not override those methods, the default im- method. plementation provided in the interface will be executed. These operators are from the original proposal [10]. Other opera- interface A { default void m() tors were introduced in further works (a comprehensive list of op- {out.println("Hi, I’m interface A");} erators with relations among them can be found in [5]). We focus } on this particular set as we think they are the most interesting ones class B implements A {} from a programming point of view. //doesn’t override m The original definition of traits says that trait and class usages are separated: the first ones are units of reuse, while the second ones public class FirstDM { are generator of instances. A class can be specified by composing public static void main(String[] args) { a superclass with a set of traits and some glue methods (aka glue B b = new B (); code).
Load more

Recommended publications
  • Mixins and Traits
    ◦ ◦◦◦ TECHNISCHE UNIVERSITAT¨ MUNCHEN¨ ◦◦◦◦ ◦ ◦ ◦◦◦ ◦◦◦◦ ¨ ¨ ◦ ◦◦ FAKULTAT FUR INFORMATIK Programming Languages Mixins and Traits Dr. Michael Petter Winter 2016/17 What advanced techiques are there besides multiple implementation inheritance? Outline Design Problems Cons of Implementation Inheritance 1 Inheritance vs Aggregation 1 2 (De-)Composition Problems Lack of finegrained Control 2 Inappropriate Hierarchies Inheritance in Detail A Focus on Traits 1 A Model for single inheritance 1 2 Inheritance Calculus with Separation of Composition and Inheritance Expressions Modeling 2 3 Modeling Mixins Trait Calculus Mixins in Languages Traits in Languages 1 (Virtual) Extension Methods 1 Simulating Mixins 2 Squeak 2 Native Mixins Reusability ≡ Inheritance? Codesharing in Object Oriented Systems is often inheritance-centric. Inheritance itself comes in different flavours: I single inheritance I multiple inheritance All flavours of inheritance tackle problems of decomposition and composition The Adventure Game Door ShortDoor LockedDoor canPass(Person p) canOpen(Person p) ? ShortLockedDoor canOpen(Person p) canPass(Person p) The Adventure Game Door <interface>Doorlike canPass(Person p) canOpen(Person p) Short canPass(Person p) Locked canOpen(Person p) ShortLockedDoor ! Aggregation & S.-Inheritance Door must explicitely provide canOpen(Person p) chaining canPass(Person p) Doorlike must anticipate wrappers ) Multiple Inheritance X The Wrapper FileStream SocketStream read() read() write() write() ? SynchRW acquireLock() releaseLock() ! Inappropriate Hierarchies
    [Show full text]
  • Declaring Vars in Class Php
    Declaring Vars In Class Php Is Tobe Esculapian or misformed after aluminous Neall plopping so magnanimously? Forrest corresponds prolixly? Forbidden Osmund sometimes pargets any lilliputian yell guardedly. How variable as int, php in using interpolation rather than configured one of people prefer to override whatever information useful whenever you call it leads to expose parts that We daily work with advertisers relevant to our readers. Acceptable in php programmers and retry saving again, declaration must be. Declaring a property but a class is an exact task use one table the keyword public protected or private followed by a normal variable declaration If. If you wrong there holding an IE bug with var a foo only declaring a global for file scope. Your class declaration format is declared protected field? You help also define methods in the class that allow tool to manipulate the values of object properties and perform operations on objects. PHP Class Properties Tutorials by Supun Kavinda. An amazon associate we declare the class in declarations as containers for our clients in the usages of a name given client exits and in? How clean and in declaring a class declaration scope in the vars of that are their parent selector. Using long array syntax array 1 2 3 for declaring arrays is generally. By declaring a class declaration, classes and see for? It turns out some interview situations, every time to magento source and other class names but you have a common occurrence, therefore considered a value. The var keyword in PHP is used to declare the property or variable of class which is primitive by default The var keyword is alike as out when declaring variables or root of a class Note The var keyword was deprecated from version 50.
    [Show full text]
  • Learning Javascript Design Patterns
    Learning JavaScript Design Patterns Addy Osmani Beijing • Cambridge • Farnham • Köln • Sebastopol • Tokyo Learning JavaScript Design Patterns by Addy Osmani Copyright © 2012 Addy Osmani. All rights reserved. Revision History for the : 2012-05-01 Early release revision 1 See http://oreilly.com/catalog/errata.csp?isbn=9781449331818 for release details. ISBN: 978-1-449-33181-8 1335906805 Table of Contents Preface ..................................................................... ix 1. Introduction ........................................................... 1 2. What is a Pattern? ...................................................... 3 We already use patterns everyday 4 3. 'Pattern'-ity Testing, Proto-Patterns & The Rule Of Three ...................... 7 4. The Structure Of A Design Pattern ......................................... 9 5. Writing Design Patterns ................................................. 11 6. Anti-Patterns ......................................................... 13 7. Categories Of Design Pattern ............................................ 15 Creational Design Patterns 15 Structural Design Patterns 16 Behavioral Design Patterns 16 8. Design Pattern Categorization ........................................... 17 A brief note on classes 17 9. JavaScript Design Patterns .............................................. 21 The Creational Pattern 22 The Constructor Pattern 23 Basic Constructors 23 Constructors With Prototypes 24 The Singleton Pattern 24 The Module Pattern 27 iii Modules 27 Object Literals 27 The Module Pattern
    [Show full text]
  • Mixin-Based Programming in C++1
    Mixin-Based Programming in C++1 Yannis Smaragdakis Don Batory College of Computing Department of Computer Sciences Georgia Institute of Technology The University of Texas at Austin Atlanta, GA 30332 Austin, Texas 78712 [email protected] [email protected] Abstract. Combinations of C++ features, like inheritance, templates, and class nesting, allow for the expression of powerful component patterns. In particular, research has demonstrated that, using C++ mixin classes, one can express lay- ered component-based designs concisely with efficient implementations. In this paper, we discuss pragmatic issues related to component-based programming using C++ mixins. We explain surprising interactions of C++ features and poli- cies that sometimes complicate mixin implementations, while other times enable additional functionality without extra effort. 1 Introduction Large software artifacts are arguably among the most complex products of human intellect. The complexity of software has led to implementation methodologies that divide a problem into manageable parts and compose the parts to form the final prod- uct. Several research efforts have argued that C++ templates (a powerful parameteriza- tion mechanism) can be used to perform this division elegantly. In particular, the work of VanHilst and Notkin [29][30][31] showed how one can implement collaboration-based (or role-based) designs using a certain templatized class pattern, known as a mixin class (or just mixin). Compared to other techniques (e.g., a straightforward use of application frameworks [17]) the VanHilst and Notkin method yields less redundancy and reusable components that reflect the structure of the design. At the same time, unnecessary dynamic binding can be eliminated, result- ing into more efficient implementations.
    [Show full text]
  • A Foundation for Trait-Based Metaprogramming
    A foundation for trait-based metaprogramming John Reppy Aaron Turon University of Chicago {jhr, adrassi}@cs.uchicago.edu Abstract We present a calculus, based on the Fisher-Reppy polymorphic Scharli¨ et al. introduced traits as reusable units of behavior inde- trait calculus [FR03], with support for trait privacy, hiding and deep pendent of the inheritance hierarchy. Despite their relative simplic- renaming of trait methods, and a more granular trait typing. Our ity, traits offer a surprisingly rich calculus. Trait calculi typically in- calculus is more expressive (it provides new forms of conflict- clude operations for resolving conflicts when composing two traits. resolution) and more flexible (it allows after-the-fact renaming) In the existing work on traits, these operations (method exclusion than the previous work. Traits provide a useful mechanism for shar- and aliasing) are shallow, i.e., they have no effect on the body of the ing code between otherwise unrelated classes. By adding deep re- other methods in the trait. In this paper, we present a new trait sys- naming, our trait calculus supports sharing code between methods. tem, based on the Fisher-Reppy trait calculus, that adds deep oper- For example, the JAVA notion of synchronized methods can im- ations (method hiding and renaming) to support conflict resolution. plemented as a trait in our system and can be applied to multiple The proposed operations are deep in the sense that they preserve methods in the same class to produce synchronized versions. We any existing connections between the affected method and the other term this new use of traits trait-based metaprogramming.
    [Show full text]
  • Programming Languages
    ◦ ◦◦◦ TECHNISCHE UNIVERSITAT¨ MUNCHEN¨ ◦◦◦◦ ◦ ◦ ◦◦◦ ◦◦◦◦ ¨ ¨ ◦ ◦◦ FAKULTAT FUR INFORMATIK Programming Languages Traits Dr. Axel Simon and Dr. Michael Petter Winter term 2012 Traits 1 / 30 “Is Multiple Inheritance the holy grail of reusability?“ Learning outcomes 1 Identify problems of composition and decomposition 2 Understand semantics of traits 3 Separate function provision, object generation and class relations 4 Traits and existing program languages Traits Introduction 2 / 30 Reusability ≡ Inheritance? Codesharing in Object Oriented Systems is usually inheritance-centric. Inheritance itself comes in different flavours: I single inheritance I multiple inheritance I mixin inheritance All flavours of inheritance tackle problems of decomposition and composition Traits Problems with Inheritance and Composability 3 / 30 Streams FileStream SynchRW SocketStream read() acquireLock() read() write() releaseLock() write() read() write() SynchedFileStream SynchedSocketStream ! Duplicated Wrappers Multiple Inheritance is not applicable as super-References are statically bound ( Alternative: Mixins) Traits Problems with Inheritance and Composability Decomposition Problems 4 / 30 Streams modified FileStream SynchRW SocketStream read() acquireLock() read() write() releaseLock() write() SynchedFileStream SynchedSocketStream read() read() write() write() ! Duplicated Features read/write Code is essentially identical but duplicated Traits Problems with Inheritance and Composability Decomposition Problems 5 / 30 Oh my god, streams! SynchRW acquireLock() releaseLock()
    [Show full text]
  • A Fully In-Browser Client and Server Web Application Debug and Test Environment
    LIBERATED: A fully in-browser client and server web application debug and test environment Derrell Lipman University of Massachusetts Lowell Abstract ging and testing the entire application, both frontend and backend, within the browser environment. Once the ap- Traditional web-based client-server application devel- plication is tested, the backend portion of the code can opment has been accomplished in two separate pieces: be moved to the production server where it operates with the frontend portion which runs on the client machine has little, if any, additional debugging. been written in HTML and JavaScript; and the backend portion which runs on the server machine has been writ- 1.1 Typical web application development ten in PHP, ASP.net, or some other “server-side” lan- guage which typically interfaces to a database. The skill There are many skill sets required to implement a sets required for these two pieces are different. modern web application. On the client side, initially, the In this paper, I demonstrate a new methodology user interface must be defined. A visual designer, in con- for web-based client-server application development, in junction with a human-factors engineer, may determine which a simulated server is built into the browser envi- what features should appear in the interface, and how to ronment to run the backend code. This allows the fron- best organize them for ease of use and an attractive de- tend to issue requests to the backend, and the developer sign. to step, using a debugger, directly from frontend code into The language used to write the user interface code is backend code, and to debug and test both the frontend most typically JavaScript [6].
    [Show full text]
  • Pug-Mixins Documentation Release 0.0.2
    pug-mixins Documentation Release 0.0.2 Álvaro Mondéjar Rubio Aug 18, 2018 User’s guide 1 Installation 1 1.1 Manual..................................................1 1.2 Command line..............................................1 1.2.1 Linux..............................................1 1.2.2 Windows............................................1 2 Basic usage 3 3 Custom contexts 5 4 Reference 7 4.1 audio/ — Podcasts and playlists...................................7 4.1.1 ivoox.pug – Ivoox podcasts players...............................7 4.1.2 soundcloud.pug – Soundcloud podcasts players..................... 11 4.2 blog/ — Blogging tools........................................ 13 4.2.1 storify.pug - Storify stories................................ 13 4.3 board/ — Content-boards....................................... 14 4.3.1 livebinders.pug - Livebinders boards.......................... 14 4.3.2 padlet.pug – Content boards from Padlet............................ 15 4.4 code/ — Programming tools..................................... 17 4.4.1 codepen.pug – Modern pens................................ 17 4.4.2 console.pug – Insert consoles everywhere........................ 18 4.4.3 gist.pug – Github gists mixins............................... 19 4.4.4 jsfiddle.pug – JsFiddle web editor............................ 20 4.4.5 pastebin.pug – Clean Pastebin pastes........................... 22 4.4.6 pythontutor.pug – Code executions step by step..................... 23 4.4.7 shield.pug – Developer shields.............................. 24 4.5 crypto/
    [Show full text]
  • The Scala Programming Language
    The Scala Programming Language Mooly Sagiv Slides taken from Martin Odersky (EPFL) Donna Malayeri (CMU) Hila Peleg (TAU) Modern Functional Programming • Higher order • Modules • Pattern matching • Statically typed with type inference • Two viable alternatives • Haskel • Pure lazy evaluation and higher order programming leads to Concise programming • Support for domain specific languages • I/O Monads • Type classes • OCaml • Encapsulated side-effects via references Then Why aren’t FP adapted? • Education • Lack of OO support • Subtyping increases the complexity of type inference • Programmers seeks control on the exact implementation • Imperative programming is natural in certain situations Why Scala? (Coming from OCaml) • Runs on the JVM/.NET • Can use any Java code in Scala • Combines functional and imperative programming in a smooth way • Effective library • Inheritance • General modularity mechanisms The Java Programming Language • Designed by Sun 1991-95 • Statically typed and type safe • Clean and Powerful libraries • Clean references and arrays • Object Oriented with single inheritance • Interfaces with multiple inhertitence • Portable with JVM • Effective JIT compilers • Support for concurrency • Useful for Internet Java Critique • Downcasting reduces the effectiveness of static type checking • Many of the interesting errors caught at runtime • Still better than C, C++ • Huge code blowouts • Hard to define domain specific knowledge • A lot of boilerplate code • Sometimes OO stands in our way • Generics only partially helps Why
    [Show full text]
  • Export Declare Class Typescript
    Export Declare Class Typescript Transcendent Gilbert electroplating her designment so cringingly that Hamlin electrifies very astronomically. euphonisingMordacious Olafalmost never transmutably, deloused so though briefly Hari or lanced anthologised any communard his debentures penitently. shine. Curst and unbookish Lee Extra level it gets from a lot of imports and export class We will be exported declarations, export a class variables. In typescript fies directly on ide gives you export declare class typescript class from which has properties described later on github example. The typescript constants is cleanest way to export declare class typescript. They are respected by following is not yet implemented in mind, you like the compiler options object literals have found a declaration. To only use this is of guaranteeing safety. When there is stack memory usage of this is a previously assigned to type definitions are optional params are computed member public. In typescript class, when to finish rendering, you can be used for typescript is basically, and no way. Google developer for you declare or a declaration files for examples to tell the. While implementing the. The pattern is great software concept came to find these functions from inside an application. Button component through metaprogramming syntax depends on how often used, export declare class typescript support is. Filling in case there are optional loading aspect for ribbon file if you? Consumers of a common approach, function used as below is this js documentation for all of events, omitting privately used consistently. Thank you can bundle it will be to import all contents are declaring this is being observed, if an array element, you want to protect.
    [Show full text]
  • Appendix a Setting up a Local Web Server
    Appendix A Setting Up a Local Web Server It’ll be much easier for you to run the examples in this book if you run them on a local web server. One reason for this is because of a security sandboxing feature that Internet Explorer has for running HTML files that contain JavaScript in them; the other is to replicate the manner in which you will be using Dojo for a real website or web application. Although the Mac OS X operating system includes a built-in web server as do some versions of Windows, I will be going through, step-by-step, how to install a local web server that will serve HTML, JavaScript, and PHP files. You won’t be using the included web servers built into your operating system because of the complex configurations. Instead, you will be using a turnkey solution, one for the Mac called MAMP (which stands for Macintosh, Apache, MySQL, and PHP) or one for Windows known as XAMPP (the X is for the four operating systems it supports; the other letters stand for Apache, MySQL, PHP, and Perl). These two products are great because they give you an extremely easy and straightforward method for quickly setting up a local web server that not only supports serving static files such as HTML and JavaScript files but also supports PHP and database connectivity. The best thing about both of these tools is that they are completely free to download and use. If you are on Windows, you’ll want to skip the next section and jump to “XAMPP on Windows.” MAMP on Mac OS X The latest version of MAMP supports Snow Leopard (OS X 10.6) and older.
    [Show full text]
  • Scheme with Classes, Mixins, and Traits
    Scheme with Classes, Mixins, and Traits Matthew Flatt1, Robert Bruce Findler2, and Matthias Felleisen3 1 University of Utah 2 University of Chicago 3 Northeastern University Abstract. The Scheme language report advocates language design as the com- position of a small set of orthogonal constructs, instead of a large accumulation of features. In this paper, we demonstrate how such a design scales with the ad- dition of a class system to Scheme. Specifically, the PLT Scheme class system is a collection of orthogonal linguistic constructs for creating classes in arbitrary lexical scopes and for manipulating them as first-class values. Due to the smooth integration of classes and the core language, programmers can express mixins and traits, two major recent innovations in the object-oriented world. The class system is implemented as a macro in terms of procedures and a record-type gen- erator; the mixin and trait patterns, in turn, are naturally codified as macros over the class system. 1 Growing a Language The Revised5 Report on the Scheme programming language [20] starts with the famous proclamation that “[p]rogramming languages should be designed not by piling feature on top of feature, but by removing the weaknesses and restrictions that make additional features appear necessary.” As a result, Scheme’s core expression language consists of just six constructs: variables, constants, conditionals, assignments, procedures, and function applications. Its remaining constructs implement variable definitions and a few different forms of procedure parameter specifications. Everything else is defined as a function or macro. PLT Scheme [25], a Scheme implementation intended for language experimenta- tion, takes this maxim to the limit.
    [Show full text]