Named and Default Arguments for Polymorphic Object-Oriented Languages

Total Page:16

File Type:pdf, Size:1020Kb

Named and Default Arguments for Polymorphic Object-Oriented Languages Named and default arguments for polymorphic object-oriented languages A discussion on the design implemented in the Scala language Lukas Rytz Martin Odersky Programming Methods Laboratory Programming Methods Laboratory École Polytechnique Fédérale de Lausanne École Polytechnique Fédérale de Lausanne lukas.rytz@epfl.ch martin.odersky@epfl.ch ABSTRACT The use of named arguments improves code readability by This article describes the design and implementation of named making the role of an argument explicit, and it eliminates and default arguments in the Scala programming language. the risk of confusing the positions of parameters of the same While these features are available in many other languages type, an error which cannot be caught by a type system there are significant differences in the actual implementa- otherwise. Compare the following method applications: tions. We present a design that unifies the most reason- frame.setSize(200, 300) // which one is the height? able properties for an object-oriented language and provides frame.setSize(height = 200, width = 300) new possibilities by allowing default arguments on generic and implicit parameters. We also present a solution for the Another important application for named arguments comes problem of writing a lightweight generic update function for up when using them in conjunction with default arguments, algebraic datatypes. the second concept discussed in this article. A language with default arguments allows specifying default values for Categories and Subject Descriptors the parameters of a method. These defaults are used when- ever a method application leaves some of the parameters D.3.3 [Programming Languages]: Language Constructs undefined. and Features|Procedures, functions, and subroutines With positional arguments, the only possibility to use de- faults is to leave some parameters at the end undefined. General Terms With named arguments it is possible to provide a value for Languages, Design an arbitrary subset of the parameters and use the defaults for the others. Keywords Named and default arguments are very common features and can be found in a large number of programming lan- Named arguments, default arguments, Scala guages (see section 4). We investigate how they are im- plemented in other languages and analyze how the different 1. INTRODUCTION design choices affect the interaction with other language fea- When applying a method to a set of arguments, every ar- tures such as method overriding, virtual method calls and gument expression has to be mapped to one of the method's overloading resolution. We present two new use cases for parameters. In most programming languages this mapping default arguments by allowing to use them on parameters of is defined by the position of the argument expressions in a generic type and on implicit parameters. the argument list (i.e. the nth argument defines the nth pa- The rest of this paper is structured as follows. Section rameter of the method), in which case the arguments are 2 discusses the design choices for implementing named and called positional. An alternative is using named arguments, default arguments. In section 3 we explain the compilation where the programmer explicitly mentions the parameter technique used in Scala. Section 4 compares our implemen- name that an argument expression defines. tation with other languages, and section 5 concludes. The additional verbosity of named arguments is worth- while in applications of methods with a large number of 2. DESIGN CHOICES parameters or with multiple parameters of the same type. A central constraint when extending an existing language with named and default arguments is source compatibility: the new feature should not invalidate any existing code. But Permission to make digital or hard copies of all or part of this work for even with this restriction there are a number of design deci- personal or classroom use is granted without fee provided that copies are sion to be made. not made or distributed for profit or commercial advantage and that copies While this section provides a qualitative discussion on bear this notice and the full citation on the first page. To copy otherwise, to Scala's design of named and default arguments, a more pre- republish, to post on servers or to redistribute to lists, requires prior specific cise description of the semantics, defined by a translation permission and/or a fee. SAC’10 March 22-26, 2010, Sierre, Switzerland. into equivalent code without parameter names or defaults, Copyright 2010 ACM 978-1-60558-638-0/10/03 ...$10.00. can be found in the Scala language specification [11]. 2.1 Flexibility 2.3 Interaction with other features Our implementation of named and default arguments is This section describes how an elaborate integration of designed to provide a high degree of flexibility for the pro- named and default arguments with other language features grammer. A first fundamental decision is whether the use enables a number of useful programming patterns. of named arguments should be optional or not. We decided to make them optional because this gives the programmer 2.3.1 Curried method definitions more flexibility when calling a method, and it does not force In Scala, methods can have multiple parameter lists. Method him to chose which parameters should be named when defin- definitions with more than one parameter list are called cur- ing a method. It also allows using named arguments when ried because they allow partial application. calling a method that was written before named arguments When writing a curried method definition, default argu- were available in the language, because there is no change ments can depend on earlier parameters of the same method. in the way parameters are defined. In other words, the parameters are visible not only in the A disadvantage of enabling named arguments on all pa- method body, but also in all subsequent parameter lists. rameters is that parameter names immediately become part This enables the programmer to specify meaningful default of the public interface of a method, and changing them can arguments in some additional situations: invalidate client code. This is also true for source code which was written before named arguments were available in the def resizeImage(i: Image)(h: Int = i.height, language. Presumably, programmers were less careful in w: Int = i.width) = { .. } choosing parameter names in the past because they expected them to be private. To solve the ambiguity between a partially applied method and a method application using default arguments, Scala When using named arguments, Scala allows to specify the uses default arguments only for completing underspecified parameters in a different order than in the method defini- arguments lists. In order to use the default arguments of the tion. We also allow mixing positional and named arguments, above definition, an empty argument list has to be provided, in this case all positional arguments have to appear left of i.e. resizeImage(myImage)(). the named arguments. Unlike for instance C# 4.0 [4] where only the last parameters of a method are allowed to have de- 2.3.2 Overriding and virtual method calls faults, any parameter can have a default argument in Scala. When a method is being overridden in a subclass, the pa- rameter names of the overriding method do not need to be 2.2 Evaluation order the same as in the superclass. For type-checking an appli- Unlike OCaml [10] or ADA95 [8], Scala has a definite eval- cation which uses named arguments, the static type of the uation order for method arguments. Thus, we need to define method determines which names have to be used. However an evaluation order in the presence of named and default the actual method which is called is still resolved dynam- arguments. Given that positional arguments are evaluated ically: even if an application uses the parameter names of left-to-right, the same is done for named arguments. So in a superclass, an implementation of a subclass with different parameter names might be called. The following example the following example, a() is always evaluated before b(), no matter what the order of parameters in the method def- illustrates this behavior: inition is. trait A{ def f(a: Int, b: Int): Int = a + b m(y = a(), x = b()) } When an argument list of an application is completed with class B extends A{ default arguments, the default expressions are evaluated af- override def f(x: Int, y: Int) = x - y ter the specified arguments of that parameter list. The de- } val new fault arguments which are used in a particular application a: A = B a.f(b = 2, a = 3) // returns 1 behave just like specified arguments: they are evaluated ex- actly once, except if the corresponding parameter is a by- With the ability to choose parameter names freely it is name parameter, in which case they are evaluated every time possible to re-use a parameter name from the superclass for the method body refers to the parameter. Default expres- a different parameter in the subclass. Doing so should be sions which are not used in a method application are not avoided because it can can lead to unexpected errors when evaluated. changing a type to a more specific one: If an application has multiple argument lists (see 2.3.1), these are always evaluated left-to-right. This implies that trait A{ def f(a: Int, b: Int): Int } default expressions used in the first argument list are evalu- class B extends A{ def f(b: Int, a: Int) = b - a } ated before any arguments of the second argument list. The following, slightly tricky example illustrates evalu- val b = new B ation of default arguments. First, the default expression (b: A).f(a = 3, b = 2) // returns 1 {i += 1; i} is evaluated, then the specified argument i, and b.f(a = 3, b = 2) // returns -1 finally the default expression {i += 2; i}.
Recommended publications
  • Practical Perl Tools: Scratch the Webapp Itch With
    last tIme, we had the pleasure oF exploring the basics of a Web applica- DaviD n. BLank-EdeLman tion framework called CGI::Application (CGI::App). I appreciate this particular pack- age because it hits a certain sweet spot in practical Perl tools: terms of its complexity/learning curve and scratch the webapp itch with power. In this column we’ll finish up our exploration by looking at a few of the more CGI::Application, part 2 powerful extensions to the framework that David N. Blank-Edelman is the director of can really give it some oomph. technology at the Northeastern University College of Computer and Information Sci- ence and the author of the O’Reilly book Quick review Automating System Administration with Perl (the second edition of the Otter book), Let’s do a really quick review of how CGI::App available at purveyors of fine dead trees works, so that we can build on what we’ve learned everywhere. He has spent the past 24+ years as a system/network administrator in large so far. CGI::App is predicated on the notion of “run multi-platform environments, including modes.” When you are first starting out, it is easi- Brandeis University, Cambridge Technology est to map “run mode” to “Web page” in your head. Group, and the MIT Media Laboratory. He was the program chair of the LISA ’05 confer- You write a piece of code (i.e., a subroutine) that ence and one of the LISA ’06 Invited Talks will be responsible for producing the HTML for co-chairs.
    [Show full text]
  • Object Oriented Programming in Java Object Oriented
    Object Oriented Programming in Java Introduction Object Oriented Programming in Java Introduction to Computer Science II I Java is Object-Oriented I Not pure object oriented Christopher M. Bourke I Differs from other languages in how it achieves and implements OOP [email protected] functionality I OOP style programming requires practice Objects in Java Objects in Java Java is a class-based OOP language Definition Contrast with proto-type based OOP languages A class is a construct that is used as a blueprint to create instances of I Example: JavaScript itself. I No classes, only instances (of objects) I Constructed from nothing (ex-nihilo) I Objects are concepts; classes are Java’s realization of that concept I Inheritance through cloning of original prototype object I Classes are a definition of all objects of a specific type (instances) I Interface is build-able, mutable at runtime I Classes provide an explicit blueprint of its members and their visibility I Instances of a class must be explicitly created Objects in Java Objects in JavaI Paradigm: Singly-Rooted Hierarchy Object methods 1 //ignore: 2 protected Object clone(); 3 protected void finalize(); I All classes are subclasses of Object 4 Class<? extends Object> getClass(); 5 I Object is a java object, not an OOP object 6 //multithreaded applications: I Makes garbage collection easier 7 public void notify(); 8 public void notifyAll(); I All instances have a type and that type can be determined 9 public void wait(); I Provides a common, universal minimum interface for objects 10 public
    [Show full text]
  • Better PHP Development I
    Better PHP Development i Better PHP Development Copyright © 2017 SitePoint Pty. Ltd. Cover Design: Natalia Balska Notice of Rights All rights reserved. No part of this book may be reproduced, stored in a retrieval system or transmitted in any form or by any means, without the prior written permission of the publisher, except in the case of brief quotations embodied in critical articles or reviews. Notice of Liability The author and publisher have made every effort to ensure the accuracy of the information herein. However, the information contained in this book is sold without warranty, either express or implied. Neither the authors and SitePoint Pty. Ltd., nor its dealers or distributors will be held liable for any damages to be caused either directly or indirectly by the instructions contained in this book, or by the software or hardware products described herein. Trademark Notice Rather than indicating every occurrence of a trademarked name as such, this book uses the names only in an editorial fashion and to the benefit of the trademark owner with no intention of infringement of the trademark. Published by SitePoint Pty. Ltd. 48 Cambridge Street Collingwood VIC Australia 3066 Web: www.sitepoint.com Email: [email protected] ii Better PHP Development About SitePoint SitePoint specializes in publishing fun, practical, and easy-to-understand content for web professionals. Visit http://www.sitepoint.com/ to access our blogs, books, newsletters, articles, and community forums. You’ll find a stack of information on JavaScript, PHP, design,
    [Show full text]
  • Introducing Javascript OSA
    Introducing JavaScript OSA Late Night SOFTWARE Contents CHAPTER 1 What is JavaScript OSA?....................................................................... 1 The OSA ........................................................................................................................ 2 Why JavaScript? ............................................................................................................ 3 CHAPTER 2 JavaScript Examples.............................................................................. 5 Learning JavaScript ....................................................................................................... 6 Sieve of Eratosthenes..................................................................................................... 7 Word Histogram Example ............................................................................................. 8 Area of a Polygon .......................................................................................................... 9 CHAPTER 3 The Core Object ................................................................................... 13 Talking to the User ...................................................................................................... 14 Places ........................................................................................................................... 14 Where Am I?................................................................................................................ 14 Who Am I? .................................................................................................................
    [Show full text]
  • Concepts in Programming Languages Practicalities
    Concepts in Programming Languages Practicalities I Course web page: Alan Mycroft1 www.cl.cam.ac.uk/teaching/1617/ConceptsPL/ with lecture slides, exercise sheet and reading material. These slides play two roles – both “lecture notes" and “presentation material”; not every slide will be lectured in Computer Laboratory detail. University of Cambridge I There are various code examples (particularly for 2016–2017 (Easter Term) JavaScript and Java applets) on the ‘materials’ tab of the course web page. I One exam question. www.cl.cam.ac.uk/teaching/1617/ConceptsPL/ I The syllabus and course has changed somewhat from that of 2015/16. I would be grateful for comments on any remaining ‘rough edges’, and for views on material which is either over- or under-represented. 1Acknowledgement: various slides are based on Marcelo Fiore’s 2013/14 course. Alan Mycroft Concepts in Programming Languages 1 / 237 Alan Mycroft Concepts in Programming Languages 2 / 237 Main books Context: so many programming languages I J. C. Mitchell. Concepts in programming languages. Cambridge University Press, 2003. Peter J. Landin: “The Next 700 Programming Languages”, I T.W. Pratt and M. V.Zelkowitz. Programming Languages: CACM (published in 1966!). Design and implementation (3RD EDITION). Some programming-language ‘family trees’ (too big for slide): Prentice Hall, 1999. http://www.oreilly.com/go/languageposter http://www.levenez.com/lang/ ? M. L. Scott. Programming language pragmatics http://rigaux.org/language-study/diagram.html (4TH EDITION). http://www.rackspace.com/blog/ Elsevier, 2016. infographic-evolution-of-computer-languages/ I R. Harper. Practical Foundations for Programming Plan of this course: pick out interesting programming-language Languages.
    [Show full text]
  • The C Programming Language
    The C programming Language The C programming Language By Brian W. Kernighan and Dennis M. Ritchie. Published by Prentice-Hall in 1988 ISBN 0-13-110362-8 (paperback) ISBN 0-13-110370-9 Contents ● Preface ● Preface to the first edition ● Introduction 1. Chapter 1: A Tutorial Introduction 1. Getting Started 2. Variables and Arithmetic Expressions 3. The for statement 4. Symbolic Constants 5. Character Input and Output 1. File Copying 2. Character Counting 3. Line Counting 4. Word Counting 6. Arrays 7. Functions 8. Arguments - Call by Value 9. Character Arrays 10. External Variables and Scope 2. Chapter 2: Types, Operators and Expressions 1. Variable Names 2. Data Types and Sizes 3. Constants 4. Declarations http://freebooks.by.ru/view/CProgrammingLanguage/kandr.html (1 of 5) [5/15/2002 10:12:59 PM] The C programming Language 5. Arithmetic Operators 6. Relational and Logical Operators 7. Type Conversions 8. Increment and Decrement Operators 9. Bitwise Operators 10. Assignment Operators and Expressions 11. Conditional Expressions 12. Precedence and Order of Evaluation 3. Chapter 3: Control Flow 1. Statements and Blocks 2. If-Else 3. Else-If 4. Switch 5. Loops - While and For 6. Loops - Do-While 7. Break and Continue 8. Goto and labels 4. Chapter 4: Functions and Program Structure 1. Basics of Functions 2. Functions Returning Non-integers 3. External Variables 4. Scope Rules 5. Header Files 6. Static Variables 7. Register Variables 8. Block Structure 9. Initialization 10. Recursion 11. The C Preprocessor 1. File Inclusion 2. Macro Substitution 3. Conditional Inclusion 5. Chapter 5: Pointers and Arrays 1.
    [Show full text]
  • 210 CHAPTER 7. NAMES and BINDING Chapter 8
    210 CHAPTER 7. NAMES AND BINDING Chapter 8 Expressions and Evaluation Overview This chapter introduces the concept of the programming environment and the role of expressions in a program. Programs are executed in an environment which is provided by the operating system or the translator. An editor, linker, file system, and compiler form the environment in which the programmer can enter and run programs. Interac- tive language systems, such as APL, FORTH, Prolog, and Smalltalk among others, are embedded in subsystems which replace the operating system in forming the program- development environment. The top-level control structure for these subsystems is the Read-Evaluate-Write cycle. The order of computation within a program is controlled in one of three basic ways: nesting, sequencing, or signaling other processes through the shared environment or streams which are managed by the operating system. Within a program, an expression is a nest of function calls or operators that returns a value. Binary operators written between their arguments are used in infix syntax. Unary and binary operators written before a single argument or a pair of arguments are used in prefix syntax. In postfix syntax, operators (unary or binary) follow their arguments. Parse trees can be developed from expressions that include infix, prefix and postfix operators. Rules for precedence, associativity, and parenthesization determine which operands belong to which operators. The rules that define order of evaluation for elements of a function call are as follows: • Inside-out: Evaluate every argument before beginning to evaluate the function. 211 212 CHAPTER 8. EXPRESSIONS AND EVALUATION • Outside-in: Start evaluating the function body.
    [Show full text]
  • Session-Ocaml: a Session-Based Library with Polarities and Lenses
    Session-ocaml: a Session-based Library with Polarities and Lenses Keigo Imai1, Nobuko Yoshida2, and Shoji Yuen3 1 Gifu University, Japan 2 Imperial College London, UK 3 Nagoya University, Japan Abstract. We propose session-ocaml, a novel library for session-typed concurrent/distributed programming in OCaml. Our technique solely relies on parametric polymorphism, which can encode core session type structures with strong static guarantees. Our key ideas are: () polarised session types, which give an alternative formulation of duality enabling OCaml to automatically infer an appropriate session type in a session with a reasonable notational overhead; and () a parameterised monad with a data structure called ‘slots’ manipulated with lenses, which can statically enforce session linearity and delegations. We show applications of session-ocaml including a travel agency usecase and an SMTP protocol. Introduction Session types [], from their origins in the 휋-calculus [ ], serve as rigorous specifications for coordinating link mobility in the sense that a communication link can move among participants, while ensuring type safety. In session type systems such mobility is called delegation. Once the ownership of a session is delegated (transferred) to another participant, it cannot be used anymore at the sender side. This property is called linearity of sessions and appears indispensable for all session type systems. Linearity of session channels, however, is a major obstacle to adopt session type disciplines in mainstream languages, as it requires special syntax extensions for session communications [], or depends on specific language features, such as type-level functions in Haskell [, , , ], and affine types in Rust [], or even falling back on run-time and dynamic checking [, , , ].
    [Show full text]
  • Default Argument in Function Declaration
    Default Argument In Function Declaration Rory usually desulphurizes semasiologically or outgas subject when lopped Dani circularising colossally and nonchalantly. craunchesDewey masculinized her judgeship. weirdly if ungummed Demetris slims or cased. Teodoro is bituminous: she retes spiritoso and The actual call In declarations are declaring more organized, and declare an optional argument. The following function checks that is that can be combined with whitespace and assign values given general syntax can modify its local variables. Default parameters are declared in declarations in this is notoriously confusing at last two? Which function will you choose to owe two words? In typedefs, the logic required within the method implementation can be messy and hard to maintain. The value returned by a function is general value less the another expression evaluated, because it shut CHANGE. We learned all about how functions can accept different arguments and different styles by which we can pass those arguments in. Default values are specified during function declaration but there is no change in function definition. Input: an array of Promises. You can seize any function of that type call the argument for fidelity first parameter. First, and takes longer to write. Or counter this a typo? Default arguments are overwritten when calling function provides values for them. These examples assume common meanings of prefixes. In default parameter declaration of declaring a function is declared, this behavior of contents open file for. The parameter name is used in the implementation of the function. Optional parameters must conclude after the required parameters. This form style overrides are and two arguments in lots of parentheses.
    [Show full text]
  • Developing PHP Applications for IBM Database Servers
    Front cover Developing PHP Applications for IBM Data Servers Develop and deploy Web solutions using PHP and IBM data servers See PHP with DB2, Informix IDS, and Cloudscape examples Port PHP applications from MySQL to DB2 Whei-Jen Chen Holger Kirstein Daniel Krook Kiran H Nair Piotr Pietrzak ibm.com/redbooks International Technical Support Organization Developing PHP Applications for IBM Data Servers May 2006 SG24-7218-00 Note: Before using this information and the product it supports, read the information in “Notices” on page xi. First Edition (May 2006) This edition applies to DB2 UDB Version 8.2, Informix IDS Version 10, PHP Versions 4 and 5, Apache 1.3, and Apache 2. © Copyright International Business Machines Corporation 2006. All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. Contents Figures . vii Tables . ix Notices . xi Trademarks . xii Preface . xiii The team that wrote this redbook. xiii Acknowledgement. xv Become a published author . xvi Comments welcome. xvi Chapter 1. Technology overview . 1 1.1 Web application environment . 2 1.1.1 Web application advantages . 2 1.1.2 Web application challenges . 3 1.1.3 The state of the Web application world . 4 1.1.4 Web application components . 4 1.2 IBM data servers . 5 1.2.1 DB2 data server . 5 1.2.2 Informix database server family . 8 1.2.3 Cloudscape . 10 1.3 HTTP Servers . 11 1.3.1 Apache HTTP Server . 12 1.3.2 IBM HTTP Server . 15 1.3.3 Which Web server do I choose? .
    [Show full text]
  • Python Tutorial Python Tutorial I the First Python Program: Hello.Py Syntax Based Types Strongly Type Language Strings
    Python Tutorial by OSOE Project. Details Python Tutorial I Details The First Python Program: hello.py Details Writing a script in Python to output “Hello World” on the screen can be as simple as 1,2,3. When, writing a Python program, it is useful to write it in a text editor and then save it with a .py extension. In python, there are three differents types of files ; the files with .py extension are the Python script files, the files ending .pyc represent the compiled files and the ones with .pyo extension represent the optimized byte code files. Usually, most people produce the .py files and the system handles the rest. #!/usr/bin/python invocation tells the Operating System that the Python intepreter is needed to execute this file. It is also important to change the executions rights by using the commands chmod +x hello.py. This command will now make the hello.py an executable file. Afterwards, ./hello.py automatically invokes the python interpreter which reads and interpretes the hello.py file. Unlike other languages, it is possible to write a simple python program with any variables or function definitions just type in the keyword print followed by the expression you want to print and then run your program. Syntax Details The syntax of a python code is pretty straightforward. Generally, the syntax consists of #!/usr/bin/python invocation followed by a list of statements. These statements can be of different kinds: variables declarations, function declarations, control flow statements, loops, etc. In Python, whenever a file is read, all the statements are executed contrary to other languages like C or Java where they only compiled.
    [Show full text]
  • How to Link Tables Using SQL Named Parameters"
    How to Link Tables Using SQL Named Parameters Distributed by The OpenOffice.org Documentation Project OpenOffice.org Documentation Project How-To Table of Contents Introduction.................................................................................................................................................. 3 Creating the Database, Tables, and Data Source..........................................................................................5 Adding Data to Tables ...............................................................................................................................10 Enabling Use of Named Parameters for the Data Source...........................................................................12 The Macro.................................................................................................................................................. 13 Creating a Form for the Data Source..........................................................................................................16 Adding a Subform...................................................................................................................................... 19 Linking the Subform to the Main Form..................................................................................................... 24 Formatting Data Fields...............................................................................................................................29 More Examples...........................................................................................................................................33
    [Show full text]