Obliq, a Language with Distributed Scope

Total Page:16

File Type:pdf, Size:1020Kb

Obliq, a Language with Distributed Scope Obliq A Language with Distributed Scope Luca Cardelli June 3, 1994 © Digital Equipment Corporation 1994 This work may not be copied or reproduced in whole or in part for any commercial purpose. Permis- sion to copy in whole or in part without payment of fee is granted for nonprofit educational and re- search purposes provided that all such whole or partial copies include the following: a notice that such copying is by permission of the Systems Research Center of Digital Equipment Corporation in Palo Alto, California; an acknowledgment of the authors and individual contributors to the work; and all applicable portions of the copyright notice. Copying, reproducing, or republishing for any other pur- pose shall require a license with payment of fee to the Systems Research Center. All rights reserved. Abstract Obliq is a lexically-scoped untyped interpreted language that supports distributed object-oriented computation. An Obliq computation may involve multiple threads of control within an address space, multiple address spaces on a machine, heterogeneous machines over a local network, and multiple net- works over the Internet. Obliq objects have state and are local to a site. Obliq computations can roam over the network, while maintaining network connections. Contents 1. Introduction ................................................................................................................................. 1 1.1 Language Overview ............................................................................................................. 1 1.2 Distributed Semantics ..........................................................................................................2 2. Local Objects ............................................................................................................................... 3 2.1 Objects and their Fields ........................................................................................................ 3 2.2 Object Operations ................................................................................................................ 4 2.3 Simple Examples .................................................................................................................. 6 3. Remote Objects ........................................................................................................................... 6 3.1 State ...................................................................................................................................... 7 3.2 Transmission ........................................................................................................................ 7 3.3 Distributed Computation ...................................................................................................... 8 3.4 Self-inflicted Operations ......................................................................................................9 3.5 Protected Objects.................................................................................................................. 9 3.6 Serialized Objects .............................................................................................................. 10 3.7 Name Servers ..................................................................................................................... 11 3.8 Execution Engines .............................................................................................................. 13 4. Local Techniques ...................................................................................................................... 13 4.1 Recursion and Iteration ...................................................................................................... 13 4.2 The Object-Oriented Numerals .......................................................................................... 14 4.3 The Prime Numbers Sieve ................................................................................................. 15 4.4 A Calculator ....................................................................................................................... 15 4.5 Surrogates........................................................................................................................... 17 5. Distributed Techniques.............................................................................................................. 17 5.1 A Serialized Queue............................................................................................................. 17 5.2 Compute Servers ................................................................................................................ 18 5.3 A Database Server .............................................................................................................. 19 5.4 Remote Agents ................................................................................................................... 20 5.5 Application Partitioning ..................................................................................................... 22 5.6 Agent Migration ................................................................................................................. 22 5.7 Object Migration ................................................................................................................ 22 5.8 Application Servers ............................................................................................................ 24 6. Syntax Overview ....................................................................................................................... 24 7. Conclusions ............................................................................................................................... 25 Related Work .................................................................................................................... 25 Status ................................................................................................................................. 26 Future Work ...................................................................................................................... 26 Acknowledgments ........................................................................................................................... 26 A. Language Reference .................................................................................................................. 27 A.1 Syntactic Structures ............................................................................................................ 27 A.1.1 Identifiers .................................................................................................................. 27 A.1.2 Definitions ................................................................................................................ 27 A.1.3 Terms ........................................................................................................................ 27 A.1.4 Term Sequences ........................................................................................................ 28 A.1.5 Built-In Operators ..................................................................................................... 28 A.1.6 Operator Precedence ................................................................................................. 28 A.2 Data Structures ................................................................................................................... 28 A.2.1 Value Identity ........................................................................................................... 28 A.2.2 Constants .................................................................................................................. 29 A.2.3 Operators .................................................................................................................. 29 A.2.4 Arrays ....................................................................................................................... 30 A.2.5 Options ..................................................................................................................... 30 A.2.6 Objects ...................................................................................................................... 30 A.2.7 Protection and Serialization ...................................................................................... 32 A.2.8 Object and Engine Servers........................................................................................ 32 A.2.9 Processor and File System Enablers ......................................................................... 33 A.3 Control Structures .............................................................................................................. 33 A.3.1 Definitions ................................................................................................................ 34 A.3.2 Assignment ............................................................................................................... 34 A.3.3 Sequencing ................................................................................................................ 34 A.3.4 Procedures and Methods........................................................................................... 34 A.3.5 Conditionals .............................................................................................................. 35 A.3.6 Case .........................................................................................................................
Recommended publications
  • Language-Level Support for Exploratory Programming of Distributed Virtual Environments
    In Proc ACM UIST ‘96 (Symp. on User Interface Software and Technology), Seattle, WA, November 6–8, 1996, pp. 83–94. Language-Level Support for Exploratory Programming of Distributed Virtual Environments Blair MacIntyre and Steven Feiner Department of Computer Science, Columbia University, New York, NY, 10027 {bm,feiner}@cs.columbia.edu http://www.cs.columbia.edu/~{bm,feiner} Abstract resulted in an unmanageable welter of client-server relation- ships, with each of a dozen or more processes needing to We describe COTERIE, a toolkit that provides language- create and maintain explicit connections to each other and to level support for building distributed virtual environments. handle inevitable crashes. COTERIE is based on the distributed data-object paradigm for distributed shared memory. Any data object in COTE- We spent a sufficiently large portion of our time reengineer- RIE can be declared to be a Shared Object that is replicated ing client-server code that it became clear to us that our fully in any process that is interested in it. These Shared implementation of the client-server model was unsuitable Objects support asynchronous data propagation with atomic for exploratory programming of distributed research proto- serializable updates, and asynchronous notification of types. The heart of the problem, as we saw it, was a lack of updates. COTERIE is built in Modula-3 and uses existing support for data sharing that was both efficient and easy for Modula-3 packages that support an integrated interpreted programmers to use in the face of frequent and unantici- language, multithreading, and 3D animation. Unlike other pated changes.
    [Show full text]
  • Improving the Aircraft Design Process Using Web-Based Modeling and Simulation
    Reed. J.;I.. Fdiet7, G. .j. unci AJjeh. ‘-1. ,-I Improving the Aircraft Design Process Using Web-based Modeling and Simulation John A. Reed?, Gregory J. Follenz, and Abdollah A. Afjeht tThe University of Toledo 2801 West Bancroft Street Toledo, Ohio 43606 :NASA John H. Glenn Research Center 2 1000 Brookpark Road Cleveland, Ohio 44135 Keywords: Web-based simulation, aircraft design, distributed simulation, JavaTM,object-oriented ~~ ~ ~ ~~ Supported by the High Performance Computing and Communication Project (HPCCP) at the NASA Glenn Research Center. Page 1 of35 Abstract Designing and developing new aircraft systems is time-consuming and expensive. Computational simulation is a promising means for reducing design cycle times, but requires a flexible software environment capable of integrating advanced multidisciplinary and muitifidelity analysis methods, dynamically managing data across heterogeneous computing platforms, and distributing computationally complex tasks. Web-based simulation, with its emphasis on collaborative composition of simulation models, distributed heterogeneous execution, and dynamic multimedia documentation, has the potential to meet these requirements. This paper outlines the current aircraft design process, highlighting its problems and complexities, and presents our vision of an aircraft design process using Web-based modeling and simulation. Page 2 of 35 1 Introduction Intensive competition in the commercial aviation industry is placing increasing pressure on aircraft manufacturers to reduce the time, cost and risk of product development. To compete effectively in today’s global marketplace, innovative approaches to reducing aircraft design-cycle times are needed. Computational simulation, such as computational fluid dynamics (CFD) and finite element analysis (FEA), has the potential to compress design-cycle times due to the flexibility it provides for rapid and relatively inexpensive evaluation of alternative designs and because it can be used to integrate multidisciplinary analysis earlier in the design process [ 171.
    [Show full text]
  • Introduction to the Literature on Programming Language Design Gary T
    Computer Science Technical Reports Computer Science 7-1999 Introduction to the Literature On Programming Language Design Gary T. Leavens Iowa State University Follow this and additional works at: http://lib.dr.iastate.edu/cs_techreports Part of the Programming Languages and Compilers Commons Recommended Citation Leavens, Gary T., "Introduction to the Literature On Programming Language Design" (1999). Computer Science Technical Reports. 59. http://lib.dr.iastate.edu/cs_techreports/59 This Article is brought to you for free and open access by the Computer Science at Iowa State University Digital Repository. It has been accepted for inclusion in Computer Science Technical Reports by an authorized administrator of Iowa State University Digital Repository. For more information, please contact [email protected]. Introduction to the Literature On Programming Language Design Abstract This is an introduction to the literature on programming language design and related topics. It is intended to cite the most important work, and to provide a place for students to start a literature search. Keywords programming languages, semantics, type systems, polymorphism, type theory, data abstraction, functional programming, object-oriented programming, logic programming, declarative programming, parallel and distributed programming languages Disciplines Programming Languages and Compilers This article is available at Iowa State University Digital Repository: http://lib.dr.iastate.edu/cs_techreports/59 Intro duction to the Literature On Programming Language Design Gary T. Leavens TR 93-01c Jan. 1993, revised Jan. 1994, Feb. 1996, and July 1999 Keywords: programming languages, semantics, typ e systems, p olymorphism, typ e theory, data abstrac- tion, functional programming, ob ject-oriented programming, logic programming, declarative programming, parallel and distributed programming languages.
    [Show full text]
  • Comparative Programming Languages CM20253
    We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist And there are many more factors we could talk about in making choices of language The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design The End There are many languages out there, both general purpose and specialist We have briefly covered many aspects of language design And there are many more factors we could talk about in making choices of language Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages And then the interopability of languages becomes important For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project For example, can you easily join together code written in Java and C? The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important The End Or languages Often a single project can use several languages, each suited to its part of the project And then the interopability of languages becomes important For example, can you easily
    [Show full text]
  • The Specification of Dynamic Distributed Component Systems
    CSTR The Sp ecication of Dynamic Distributed Comp onent Systems Thesis by Joseph R Kiniry In Partial Fulllment of the Requirements for the Degree of Master of Science California Institute of Technology Pasadena California Submitted May ii c Joseph R Kiniry All Rights Reserved DRAFT NOT FOR DISTRIBUTION July iii Acknowledgements Sp ecial thanks go to my wonderful advisor Dr K Mani Chandy Thanks also to Infospheres group memb ers and fellow graduate students Dan M Zimmerman Adam Rifkin and Roman Ginis Comp ositional Computing group member EveScho oler and p ostdo cs and past Comp group memb ers Dr Paolo Sivilotti Dr John Thornley and Dr Berna Massingill Dan Zimmerman was particularly helpful in his motivation to develop elegantandpowerful soft ware frameworks Adam provided the inspiration of a Webyogi and Paul is the studenttheoretician in whose fo otsteps I walk Thanks also go to Diane Go o dfellow for her administrative supp ort Finally Id like to thank my longterm partner and b est friend Mary Baxter youll always b e an inspiration in my life This work was sp onsored by the CISE directorate of the National Science Foundation under Problem Solving Environments grant CCR the Center for ResearchinParallel Computing under grant NSF CCR and byParasoft and Novell The formal metho ds and adaptivity reliability mobility security parts of the pro ject are sp onsored by the Air Force Oce of Scientic Research under grantAFOSR F DRAFT NOT FOR DISTRIBUTION July iv DRAFT NOT FOR DISTRIBUTION July v Abstract Mo dern computing systems
    [Show full text]
  • Near-Infrared Spectroscopy of Miranda
    A&A 562, A46 (2014) Astronomy DOI: 10.1051/0004-6361/201321988 & c ESO 2014 Astrophysics Near-infrared spectroscopy of Miranda F. Gourgeot1;2, C. Dumas2, F. Merlin1;3, P. Vernazza4, and A. Alvarez-Candal2;5;6 1 Observatoire de Paris-Meudon / LESIA, 92190 Meudon, France e-mail: [email protected] 2 European Southern Observatory, Alonso de Córdova 3107, 1900 Casilla Vitacura, Santiago, Chile 3 Université Denis Diderot, Paris VII, 75013 Paris, France 4 Observatoire Astronomique Marseille-Provence, 13013 Marseille, France 5 Instituto de Astrofísica de Andalucía – CSIC, Glorieta de la Astronomía S/N, 18008 Granada, Spain 6 Observatório Nacional, COAA, Rua General José Cristino 77, 20921-400 Rio de Janeiro, Brazil Received 29 May 2013 / Accepted 16 October 2013 ABSTRACT Aims. We present new near-infrared spectra of the leading and trailing hemispheres of Uranus’s icy satellite Miranda. This body is probably the most remarkable of all the satellites of Uranus, because it displays series of surface features such as faults, craters, and large-scale upwelling, a remnant of a geologically very active past. Methods. The observations were obtained with PHARO at Palomar and SpeX at the IRTF Observatory. We performed spectral modelings to further constrain the nature and the chemical and physical states of the compounds possibly present on the surface of Miranda. Results. Water ice signatures are clearly visible in the H and K bands, and it appears to be found in its crystalline state over most of the satellite’s surface. Unlike what has been found for Uranus’s outer moons, we did not find any significative differences in the abundances of ices covering the leading and trailing hemispheres of Miranda.
    [Show full text]
  • Typed Open Programming
    Typed Open Programming A higher-order, typed approach to dynamic modularity and distribution Preliminary Version Andreas Rossberg Dissertation zur Erlangung des Grades des Doktors der Ingenieurwissenschaften der Naturwissenschaftlich-Technischen Fakult¨aten der Universit¨at des Saarlandes Saarbr¨ucken, 5. Januar 2007 Dekan: Prof. Dr. Andreas Sch¨utze Erstgutachter: Prof. Dr. Gert Smolka Zweitgutachter: Prof. Dr. Andreas Zeller ii Abstract In this dissertation we develop an approach for reconciling open programming – the development of programs that support dynamic exchange of higher-order values with other processes – with strong static typing in programming languages. We present the design of a concrete programming language, Alice ML, that consists of a conventional functional language extended with a set of orthogonal features like higher-order modules, dynamic type checking, higher-order serialisation, and concurrency. On top of these a flexible system of dynamic components and a simple but expressive notion of distribution is realised. The central concept in this design is the package, a first-class value embedding a module along with its interface type, which is dynamically checked whenever the module is extracted. Furthermore, we develop a formal model for abstract types that is not invalidated by the presence of primitives for dynamic type inspection, as is the case for the standard model based on existential quantification. For that purpose, we present an idealised language in form of an extended λ-calculus, which can express dynamic generation of types. This calculus is the first to combine and explore the interference of sealing and type inspection with higher-order singleton kinds, a feature for expressing sharing constraints on abstract types.
    [Show full text]
  • A Distributed 3D Graphics Library
    A Distributed 3D Graphics Library Blair MacIntyre and Steven Feiner1 Department of Computer Science Columbia University Abstract We present Repo-3D, a general-purpose, object-oriented library for developing distributed, interactive 3D graphics applications across a range of heterogeneous workstations. Repo-3D is designed to make it easy for programmers to rapidly build prototypes using a familiar multi-threaded, object-oriented programming paradigm. All data sharing of both graphical and non-graphical data is done via general-purpose remote and replicated objects, presenting the illusion of a single distributed shared memory. Graphical objects are directly distributed, circumventing the “duplicate database” problem and allowing programmers to focus on the application details. Repo-3D is embedded in Repo, an interpreted, lexically-scoped, distributed programming language, allowing entire applications to Figure 1: Two meanings of distributed graphics: (a) a single logical be rapidly prototyped. We discuss Repo-3D’s design, and introduce graphics system with distributed components, and (b) multiple dis- the notion of local variations to the graphical objects, which allow tributed logical graphics systems. We use the second definition here. local changes to be applied to shared graphical structures. Local variations are needed to support transient local changes, such as Supported Cooperative Work (CSCW) and Distributed Virtual highlighting, and responsive local editing operations. Finally, we Environments (DVEs) have been making the transition from discuss how our approach could be applied using other program- research labs to commercial products, the term distributed graphics ming languages, such as Java. is increasingly used to refer to systems for distributing the shared CR Categories and Subject Descriptors: D.1.3 [Program- graphical state of multi-display/multi-person, distributed, interac- ming Techniques]: Concurrent Programming—Distributed Pro- tive applications (Figure 1b).
    [Show full text]
  • Local Π-Calculus at Work: Mobile Objects As Mobile Processes⋆
    Local π-Calculus at Work: Mobile Objects as Mobile Processes? Massimo Merro1??, Josva Kleist2, and Uwe Nestmann2 1 INRIA, Sophia-Antipolis, France 2 BRICS - Basic Research in Computer Science, Danish National Research Foundation, Aalborg University, Denmark Abstract. Obliq is a distributed, object-based programming language. In Obliq, the migration of an object is proposed as creating a clone of the object at the target site, whereafter the original object is turned into an alias for the clone. Obliq has an only informal semantics, so there is no proof that this style of migration is correct, i.e., transparent to object clients. In this paper, we focus on Øjeblik, an abstraction of Obliq. We give a π-calculus semantics to Øjeblik, and we use it to formally prove the correctness of object surrogation, an abstraction of object migration. 1 Introduction The work presented in this paper is in line with the research activity to use the π-calculus as a toolbox for reasoning about distributed object-oriented pro- gramming languages. Former works on the semantics of objects as processes have shown the value of this approach: while [22,9,19,10] have focused on just providing formal semantics to object-oriented languages and language features, the work of others [18,20] has been driven by a specific programming problem. Our work tackles a problem in Obliq, Cardelli’s lexically-scoped distributed pro- gramming language [4]. In this setting, Cardelli proposed to implement object migration by creating a clone of the object at the target site and then turning the original (local) object into an alias for the new (remote) object.
    [Show full text]
  • Liste De Langages De Programmation
    Liste de langages de programmation Le but de cette liste de langages de programmation est d'inclure tous les langages de programmation existants, qu'ils soient actuellement utilisés ou historiques, par ordre alphabétique. Ne sont pas listés ici les langages informatiques de représentation de données tels que XML, HTML ou YAML. Par ailleurs, cette liste répertorie les langages de programmation, et non leurs implémentations -ou "Framework"- (par exemple : JRuby et IronRuby sont deux implémentations différentes du même langage Ruby). Sommaire : Haut - A B C D E F G H I J K L M N O P Q R S T U V W X Y Z A A+ A++ A# .NET ou A# (Axiom) A-0 System ABAL ABAL++ ABAP ABC ABCL/1 ABCL/c+ ABCL/R ABCL/R2 Abel ABSET ABSYS ALI Abundance ACC Accent ActForex Ace DASL ACT-III Ada Adenine Afnix Agora AIS Balise Aikido Alef ALF Algol Alice Ambi Amiga E AML AMOS AMPLE Anubis APDL APL AppleScript Arc Arduino Ariberion Arobase (langage) Assembleur ASP.NET ATS AutoHotkey AutoIt Averest awk axe parser Axum B B BASIC BASH Bat Batch binaire bc BCPL BeanShell Befunge Bennu Bertrand BETA Bigwig Bistro BitC BLISS BLITZ BASIC BluePrint (utilisé dans Unreal Engine) Blue Bon Boo Boomerang BPEL Brainfuck BUGSYS BuildProfessional C C C-- C++ C# C/AL Caché ObjectScript Cameleon Caml Cat Cayenne Cecil Cel Cesil Ceylon CFML Cg Ch interpreter (C/C++ interpreter) Chapel (en) CHAIN Charity Chef CHILL CHIP-8 chomski CHR Chrome ChucK CICODE CICS CIL Cilk CL (Honeywell) Claire Clarion Clean Clipper CLIST Clojure CLU CMS-2 COBOL CobolScript Cobra CODE CoffeeScript Cola ColdC ColdFusion
    [Show full text]
  • Explaining Why the Satellites of Uranus Have Equatorial Prograde Orbits Despite of the Large Planet’S Obliquity
    EPSC Abstracts Vol. 6, EPSC-DPS2011-54, 2011 EPSC-DPS Joint Meeting 2011 c Author(s) 2011 Explaining why the satellites of Uranus have equatorial prograde orbits despite of the large planet’s obliquity. A. Morbidelli (1), K. Tsiganis (2), K. Batygin (3), R. Gomes (4) and A. Crida (1) (1) Observatoire de la Côte d’Azur, Nice, France, (Email: [email protected] / Fax: +33-4-92003118), (2) University of Thessaloniki, Germany, (3) Caltech, Pasadena, California, (4) Observatorio National, Rio de Janeiro, Bresil Abstract very close to the equator, for all bodies up to Oberon’s distance, due to the oblateness of the planet. We show that the existence of equatorial satellites is However, to have a resonance between the preces- not inconsistent with the collisional tilting scenario sion rate of the spin axis of Uranus and the secular for Uranus. In fact, if the planet was surrounded by frequency of precession of its orbit (as required to tilt a proto-satellite disk at the time of the tilting and a the planet slowly), the former had to be much faster massive ring of material was temporarily placed in- than now. In [2] this is achieved by assuming that side the Roche radius of the planet by the collision, the Uranus had originally a massive satellite with an or- proto-satellite disk would have started to precess inco- bital radius of about 0.01 AU (Satellite X, hereafter). herently around the equator of the planet. Collisional The problem is that the Laplace plane for Satellite X damping would then collapse it into a thin equatorial is close to the orbital plane of Uranus.
    [Show full text]
  • Software Tools
    Integrated Development Environments ! An IDE usually includes ! You should know how to use Software Tools " Source code editor (usually a debugger! with color highlighting) " Place breakpoints " Compiler or interpreter " Step through code " Tools for “build # Step over automation” (i.e., keeps # Step into track of what needs to be # Step out of… recompiled) " Examine current call-stack " Debugger " Examine values of active " Class browser (for variables languages with classes) Lecture 9 # Some debuggers allow you to change a variable value Top 20 Tools of All Time CS 212 – Fall 2007 (http://uk.gizmodo.com/) ! Examples: DrJava, Eclipse " In Eclipse: As you type, ! Debuggers are usually much gives you list of options + more effective than placing documentation print-statements Unix Programming Languages ! Original version by Ken Thompson ! Philosophy ! Some of the languages used in ! Some other languages (from a (Bell Labs) in 1969 " Almost everything is a text file Cornell’s CS Dept Yahoo list) " Little programs (utilities) to do " Java ABC, ActiveX, Ada, AMOS, APL, little tasks ! An interactive, multi-user # 100, 211, 212 AppleScript, Assembly, awk, BASIC, operating system (not the first " Connect programs with pipes & BETA, C and C++, C#, Cecil, Cilk, redirection " C, C++, C# such system, but an early one) CLU, COBOL, ColdC, cT, Curl, Delphi, # % who | sort | lpr # Many of the upper level Dylan, Dynace, Eiffel, Forth, # Print an alphabetical list of who is courses (networks, Fortran, Guile, Haskell, Icon, IDL, ! Unix is closely tied
    [Show full text]