Och Lönsamma Öppna Kommunikationssystem

Total Page:16

File Type:pdf, Size:1020Kb

Och Lönsamma Öppna Kommunikationssystem fcldüh OSI och lönsamma öppna kommunikationssystem Dokumentation av ett seminarium sammanställd av Victor S Epstein med Gunnar Sundblad Tddüh Telestyrelsen har inrättat ett anslag med syfte att medverka tiU snabb och lättillgänglig dokumentation beträffande användningen av teleanknutna informationssystem. Detta anslag förvaltas av TELDOK och skall bidraga tiU: Dokumentation vid tidigast möjliga tidpunkt av praktiska tillämpningar av teleanknutna informationssystem i arbetslivet Publicering och spridning, i förekommande fall översättning, av annars svåråtkomliga erfarenheter av teleanknutna informationssystem i arbetslivet, samt kompletteringar avsedda att öka användningsvärdet för svenska förhållanden och svenska läsare Studieresor och konferenser i direkt anknytning till arbetet med att dokumentera och sprida information beträffande praktiska tillämpningar av teleanknutna informationssystem i arbetslivet Via TELDOK är en av de skriftserier som utges av TELDOK. Via TELDOK presenterar obearbetade tillfallighetsrapporter från seminarier, studieresor osv. Hittills har utgetts: Via TELDOK 1. OSI och lönsamma öppna kommunikationssystem. Maj 1987. Av andra publikationer från TELDOK som nyligen utkommit kan nämnas: TELDOK Kapport 24. Meddelanden att använda. November 1986. TELDOK Kapport 25. Ny teleteknik i Sverige - användning i dag. November 1986. TELDOK Kapport 26. Datorstödda kunskapssystem i framtidens kontor. December 1986. TELDOK Kapport27. Inflytande och DAtorbaserade Kommunikationssystem. April 1987. TELDOK Kapport 28. Ny informationsteknologi i Japan. April 1987. TELDOK Referens dokument G. Management, usage and effects of Office Automation. April 1987. TELDOK-info 4. Att söka i databaser. Mars 1987. Publikationema kan beställas gratis dygnet runt från TeleSvar, 08-23 00 00 (med angivande av rapportnummer). Den som i fortsättningen önskar erhålla skrifter från TELDOK får automatiskt alla TELDOK Kapport och alla TELDOK-info. Ytterligare information lämnas gärna av TELDOK Kedaktionskommitté. Där ingår: Bertil Thorngren (ordförande). Televerket, 08-713 3077 Göran Axelsson, civildepartementet, 08-763 4205 Birgitta Frejhagen, LO, 08-796 2500 Peter Magnusson, TCO (ST), 08-790 5100 Agneta Qwerin, SSI/statskontoret, 08-7384862 Nils-Göran Svensson, Kiks dataförbundet, 08-24 85 55 Bengt-Ame Vedin, KTH, 08-787 8381 P G Holmlöv (sekreterare). Televerket, 08-713 4131 Adress: TELDOK, KP, Televerkets hk, 123 86 Farsta Telefaxnummer: 08-64 46 72 Förord Oöl är kortformen för Open Systems Interconnection. Ool står för utvecklingen av leverantörsobunden kommunikation. O öl handlar om att standardisera utrustning och program så att kostnadema för kommunikation drastiskt kan reduceras. iiiiiiiiiiiii ntemationell standardisering är en tidskrävande och långsam process. Projektet att utveckla kommunikationsprotokoll för överföring I av information mellan nätverk av olika struktur och design har pågått i ca 10 år. Många aktörer bland såväl användare som producenter är inblandade. Aktivitetema är många - allt från utvecklingen av nationella strategier till regler för den fysiska förbindelsen mellan två anslutningspunkter, OSI-strävandena kännetecknas av att de som så mycket annat stand- ardiseringsarbete under en lång tid endast engagerat en trängre krets; "de redan invigda". På senare tid har emellertid frågoma om att kunna kommunicera effektivt mellan olika system blivit allt angelägnare för allt fler. Att följa, påverka och satsa på detta standardiseringsarbete har blivit en angelägenhet för många såväl här hemma som i andra länder. TELDOK var en av arrangörerna bakom seminariet OSI och lönsamma öppna kommunikationssystem i slutet av oktober 1986. Seminariedeltagama erhöll en både omfattande och innehållsarik dokumentation. TELDOK har gjort bedömningen att det finns många som kan ha intresse av denna dokumentation utöver de som hade tillfalle att delta i seminariet. Vi har därför låtit mångfaldiga dokumentationen så att den lätt kan spridas. Karaktären av seminariedoku­ mentation gör sig påmind på flera sätt: bl a saknas paginering och därmed sidhänvisning i innehållsförteckningen. Det har inträffat en hel del sedan dokumentationen producerades av sina olika författare. Vi har emellertid avstått från att försöka aktualisera varje avsnitt. Skälen härtill är att det sannolikt hade blivit en så omfattande process att det i slutändan handlat om ett helt nytt material, en annan TELDOK-rapport. Vi avser att följa utvecklingen på OSI-området i syfte att åstadkomma angelägna TELDOK-rapporter. Till dess: Håll till godo med denna första introduktion! ftßmta Qjverin TELDOK Redaktionskommitté OSI-löDsanaa Bystea för öppen koammikatioa IHHEHALLSFöRTECKNING IÏLEDBIHG David Firnberg Eosys Ltd Storbrltanien: OSI Products and Plans of Equipment Suppliers In The United Kingdom DTI support for OSI: The Standards-Making Machinery Implementor Groups on OSI Standards-IGOSIS Conformance Testing OSI Opportunity Studies OSI Demonstrator Projects Björn Pehrson: Swedish Institute of Computer Science l.A New Institute 2.Design Methodology 3.Logic Programming Systems A.Knowledge Based Systems Leverantörenas synpunkter Var star vi idag? Vilka avsikter har vi inför framtiden? Digital Equipnent Anders Johansson Ericsson Information System Henrik Abraaawlcz IBM Svenska AB Karsten F. Larsen Televerkets synpunkter Carl Gustaf Vahlin plânboksfoldern:"VI lever som lär" Gunnar Ericsson, SMS (Sveriges Mekanstandardlserlng): OSI i industriell tillämpning-MAP -SHS's roll i standardiseringsarbetet fbr användare inom industrin Gunnar Sundblad SIS Att arbeta ned standardisering -SIS internationella roll och nängftriga erfarenheter BÜBEKA European Companies Initiative The European Computer and I.T. Industry Open Systems Inter-Connection (OSI) OSI — 1 Ö :rxsa;m:met sys-tem för- öjpjpen Inledning. OSI är en referensmodell som strukturerar öppna system för effektiv och enhetlig kommunikation. Inom varje skikt av modellen kommer en eller flera standarder. Utvecklingen har av olika anledningar börjat ta fart pÄ grund av använ­ darnas ökade medvetenhet och behov. Detta medför krav pä leverantörer att anpassa sig till system öppen kommunika­ tion. De nationella organisationerna för standardisering i Euro­ pa medverkar i de av EG och EFTA stödda kommisionerna CEN och CENELEC.I avsikt att inom OSI- området fft fram euro­ peiska funktionella standarder- s k FS- har en särskild kommitté bildats Joint CEN/CENELEC. Arbetet har börjat ge resultat i form av försöksstanderder betecknade ENV. Dessa kommer att bli europanormer EN vilka blir tvingande inom EG-länderna och därigenom i praktiken även inom EFTA-län­ der. Bakom detta utkast st&r Information Technology Stee­ ring Committee < ITSTC) som utgör ett samarbetsorgan för CEN, CEPT och CENELEC. < Se även sid avsnitt "Gunnar Sundblad"). Ett miniseminarium genomfördes i juni 1966 av REDU Inter­ national i samarbete med EOSYS Ltd. Därvid fick deltagarna tillfälle att lyssna till fängslande föreläsningar av David Firnberg, vd för EOSYS. England synnerligen välkänd datorexpert med tidigare erfarenheter från bl a ICL som marknadschef, vd för National Computer Center och ordfö­ rande för British Computer Society. Under ocb efter semi­ nariet framkom önskem&l om utförligare Information om var man står i Storbrltanien, Europa och Sverige beträffande utvecklingen av OSI-modellen. Under ordförandeskap av Lennart Nordström Statskontoret svarar en svensk standardiserlnskommitté <HK-31) svara för standardisering av "väsentliga dataområden" inom den grundläggande informationsteknologin. Dessa områden bear­ betas av olika arbetsgrupper. En av dem granskar ett ut­ kast till europeisk standard för provning och certifie- rlng av OSI. Forskare, leverantörer och standardiseringsexperter gav en överblick av OSI-läget 1 Sverige och hur samarbetet be­ drivs med andra instanser i Europa. Denna rapport försöker belysa seminariet som behandlade lönsamhetsaspekter p& s&väl administrativa som indust­ riella system. Dessutom berörde flera föreläsare förvän­ tade politiska initiativ inom EG och "trycket" fr&n använ­ dare. Teldok REDU och EOSYS stod som inbjudare till seminariet. Med denna rapport vill arrangörerna skapa en platform för fortsatt utveckling av öppna system för en mer effektiv och lönsam kommunikation. Denna rapport har sammanställts av Viktor S.Epstein i samarbeta med Gunnar Sundblad. Stockholm den 15 februari 1967. OSI PRODDCTS AND PLANS OF EQUIPMENT SUPPLIERS IN THE UNITED KINGDOM Advance Extract from a British Government Report, prepared with assistance from Eosys Limited, due to be published shortly David Firnberg, FBCS Managing Director Eosys Ltd and Chairman October, 1986 The Networking Centre Ltd EOSYS LIMITED GH 4AFU Clove House, The Broadway, Farnham Common, Slough SL2 3PQ Telephone: 02814 5123 Telex: 849826 EOSYS LIMITED Eosys Limited is an independent consultancy company providing expert and impartial advice, project management and related services in the application of advanced telecommunications and information technology. It places particular emphasis on the implications of the technology for users, their work and for the organisation. The company has worked with many leading organisations and has built up a unique record of experience in planning and implementing information technology. Eosys consultants have extensive experience in the human aspects of IT for the successful implementation of new equipment and procedures. Chairman of Eosys is Sir Anthony Burney OBE and Managing Director is David Firnberg, 1983/84 President of the British Computer
Recommended publications
  • How Lisp Systems Look Different in Proceedings of European Conference on Software Maintenance and Reengineering (CSMR 2008)
    How Lisp Systems Look Different In Proceedings of European Conference on Software Maintenance and Reengineering (CSMR 2008) Adrian Dozsa Tudor Gˆırba Radu Marinescu Politehnica University of Timis¸oara University of Berne Politehnica University of Timis¸oara Romania Switzerland Romania [email protected] [email protected] [email protected] Abstract rently used in a variety of domains, like bio-informatics (BioBike), data mining (PEPITe), knowledge-based en- Many reverse engineering approaches have been devel- gineering (Cycorp or Genworks), video games (Naughty oped to analyze software systems written in different lan- Dog), flight scheduling (ITA Software), natural language guages like C/C++ or Java. These approaches typically processing (SRI International), CAD (ICAD or OneSpace), rely on a meta-model, that is either specific for the language financial applications (American Express), web program- at hand or language independent (e.g. UML). However, one ming (Yahoo! Store or reddit.com), telecom (AT&T, British language that was hardly addressed is Lisp. While at first Telecom Labs or France Telecom R&D), electronic design sight it can be accommodated by current language inde- automation (AMD or American Microsystems) or planning pendent meta-models, Lisp has some unique features (e.g. systems (NASA’s Mars Pathfinder spacecraft mission) [16]. macros, CLOS entities) that are crucial for reverse engi- neering Lisp systems. In this paper we propose a suite of Why Lisp is Different. In spite of its almost fifty-year new visualizations that reveal the special traits of the Lisp history, and of the fact that other programming languages language and thus help in understanding complex Lisp sys- borrowed concepts from it, Lisp still presents some unique tems.
    [Show full text]
  • The Evolution of Lisp
    1 The Evolution of Lisp Guy L. Steele Jr. Richard P. Gabriel Thinking Machines Corporation Lucid, Inc. 245 First Street 707 Laurel Street Cambridge, Massachusetts 02142 Menlo Park, California 94025 Phone: (617) 234-2860 Phone: (415) 329-8400 FAX: (617) 243-4444 FAX: (415) 329-8480 E-mail: [email protected] E-mail: [email protected] Abstract Lisp is the world’s greatest programming language—or so its proponents think. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch. Overall, the evolution of Lisp has been guided more by institutional rivalry, one-upsmanship, and the glee born of technical cleverness that is characteristic of the “hacker culture” than by sober assessments of technical requirements. Nevertheless this process has eventually produced both an industrial- strength programming language, messy but powerful, and a technically pure dialect, small but powerful, that is suitable for use by programming-language theoreticians. We pick up where McCarthy’s paper in the first HOPL conference left off. We trace the development chronologically from the era of the PDP-6, through the heyday of Interlisp and MacLisp, past the ascension and decline of special purpose Lisp machines, to the present era of standardization activities. We then examine the technical evolution of a few representative language features, including both some notable successes and some notable failures, that illuminate design issues that distinguish Lisp from other programming languages. We also discuss the use of Lisp as a laboratory for designing other programming languages. We conclude with some reflections on the forces that have driven the evolution of Lisp.
    [Show full text]
  • Objektové Programování Poznámky K Přednášce
    Objektové programování Poznámky k přednášce Michal Krupka 18. prosince 2016 1 Obsah 1 Od Scheme k Lispu 7 1.1 Základní rozdíly mezi Schemem a Common Lispem . 8 1.2 Common Lisp: základní výbava . 14 2 Objekty a třídy 37 2.1 Základní pojmy ........................... 37 2.2 Třídy a instance v Common Lispu . 40 2.3 Inicializace slotů nových instancí . 49 ÚLOHY ................................... 52 3 Zapouzdření a polymorfismus 55 3.1 Princip zapouzdření ........................ 55 3.2 Úprava tříd point a circle ................... 61 3.3 Třída picture ........................... 64 3.4 Vlastnosti ............................... 67 3.5 Kreslení pomocí knihovny micro-graphics . 68 3.6 Kreslení grafických objektů .................... 72 3.7 Princip polymorfismu ....................... 81 3.8 Polygony ............................... 83 3.9 Geometrické transformace ..................... 87 ÚLOHY ................................... 89 4 Dědičnost 91 4.1 Princip dědičnosti a pravidlo is-a . 91 4.2 Určení předka v definici třídy ................... 98 4.3 Poznámka o běžných jazycích . 102 4.4 Přepisování metod . 102 4.5 Volání zděděné metody . 104 4.6 Inicializace instancí . 110 3 4 OBSAH 4.7 Návrh stromu dědičnosti . 111 ÚLOHY ................................... 112 5 Zpětná volání 115 5.1 Zpětná volání v knihovně micro-graphics . 115 5.2 Překreslování oken po vnější změně . 117 5.3 Překreslení při změně okna . 118 5.4 Překreslování při změnách objektů . 120 ÚLOHY ................................... 124 6 Klikání a jiné události 127 6.1 Jednoduché obsloužení vstupu z myši . 127 6.2 Zpravení grafického objektu o kliknutí . 129 6.3 Princip vlastnění, delegování, události . 133 6.4 Události ev-changing a ev-change . 136 6.5 Reakce na kliknutí: událost ev-mouse-down . 140 ÚLOHY ..................................
    [Show full text]
  • CMUCL User's Manual
    CMUCL User’s Manual Robert A. MacLachlan, Editor Mar 2009 Release 19f CMUCL is a free, high-performance implementation of the Common Lisp programming lan- guage, which runs on most major Unix platforms. It mainly conforms to the ANSI Common Lisp Standard. CMUCL features a sophisticated native-code compiler, a foreign function interface, a graphical source-level debugger, an interface to the X11 Window System, and an Emacs-like edi- tor. Keywords: lisp, Common Lisp, manual, compiler, programming language implementation, pro- gramming environment This manual is based on CMU Technical Report CMU-CS-92-161, edited by Robert A. MacLachlan, dated July 1992. Contents 1 Introduction 1 1.1 Distribution and Support . 1 1.2 Command Line Options . 2 1.3 Credits . 3 2 Design Choices and Extensions 6 2.1 Data Types . 6 2.1.1 Integers . 6 2.1.2 Floats . 6 2.1.3 Extended Floats . 9 2.1.4 Characters . 10 2.1.5 Array Initialization . 10 2.1.6 Hash tables . 10 2.2 Default Interrupts for Lisp . 11 2.3 Implementation-Specific Packages . 12 2.4 Hierarchical Packages . 13 2.4.1 Introduction . 13 2.4.2 Relative Package Names . 13 2.4.3 Compatibility with ANSI Common Lisp . 14 2.5 Package Locks . 15 2.5.1 Rationale . 15 2.5.2 Disabling package locks . 16 2.6 The Editor . 16 2.7 Garbage Collection . 16 2.7.1 GC Parameters . 17 2.7.2 Generational GC . 18 2.7.3 Weak Pointers . 19 2.7.4 Finalization . 19 2.8 Describe . 19 2.9 The Inspector .
    [Show full text]
  • Commonloops Merging Lisp and Object-Oriented Programming Daniel G
    CommonLoops Merging Lisp and Object-Oriented Programming Daniel G. Bobrow, Kenneth Kahn, Gregor Kiczales, Larry Masinter, Mark Stefik, and Frank Zdybel Xerox Palo Alto Research Center Palo Alto, California 94304 CommonLoops blends object-oriented programming Within the procedure-oriented paradigm, Lisp smoothly and tightly with the procedure-oriented provides an important approach for factoring design of Lisp. Functions and methods are combined programs that is'different from common practice in in a more general abstraction. Message passing is object-oriented programming. In this paper we inuoked via normal Lisp function call. Methods are present the linguistic mechanisms that we have viewed as partial descriptions of procedures. Lisp data developed for integrating these styles. We argue that types are integrated with object classes. With these the unification results in something greater than the integrations, it is easy to incrementally move a program sum of the parts, that is, that the mechanisms needed between the procedure and object -oriented styles. for integrating object-oriented and procedure-oriented approaches give CommonLoops surprising strength. One of the most important properties of CommonLoops is its extenswe use of meta-objects. We discuss three We describe a smooth integration of these ideas that kinds of meta-objects: objects for classes, objects for can work efficiently in Lisp systems implemented on a methods, and objects for discriminators. We argue that wide variety of machines. We chose the Common Lisp these meta-objects make practical both efficient dialect as a base on which to bui|d CommonLoops (a implementation and experimentation with new ideas Common Lisp Object-Oriented Programming System).
    [Show full text]
  • Compositional and Analytic Applications of Automated Music Notation Via Object-Oriented Programming
    UC San Diego UC San Diego Electronic Theses and Dissertations Title Compositional and analytic applications of automated music notation via object-oriented programming Permalink https://escholarship.org/uc/item/3kk9b4rv Author Trevino, Jeffrey Robert Publication Date 2013 Peer reviewed|Thesis/dissertation eScholarship.org Powered by the California Digital Library University of California UNIVERSITY OF CALIFORNIA, SAN DIEGO Compositional and Analytic Applications of Automated Music Notation via Object-oriented Programming A dissertation submitted in partial satisfaction of the requirements for the degree Doctor of Philosophy in Music by Jeffrey Robert Trevino Committee in charge: Professor Rand Steiger, Chair Professor Amy Alexander Professor Charles Curtis Professor Sheldon Nodelman Professor Miller Puckette 2013 Copyright Jeffrey Robert Trevino, 2013 All rights reserved. The dissertation of Jeffrey Robert Trevino is approved, and it is acceptable in quality and form for publication on mi- crofilm and electronically: Chair University of California, San Diego 2013 iii DEDICATION To Mom and Dad. iv EPIGRAPH Extraordinary aesthetic success based on extraordinary technology is a cruel deceit. —-Iannis Xenakis v TABLE OF CONTENTS Signature Page .................................... iii Dedication ...................................... iv Epigraph ....................................... v Table of Contents................................... vi List of Figures .................................... ix Acknowledgements ................................. xii Vita .......................................... xiii Abstract of the Dissertation . xiv Chapter 1 A Contextualized History of Object-oriented Musical Notation . 1 1.1 What is Object-oriented Programming (OOP)? . 1 1.1.1 Elements of OOP . 1 1.1.2 ANosebleed History of OOP. 6 1.2 Object-oriented Notation for Composers . 12 1.2.1 Composition as Notation . 12 1.2.2 Generative Task as an Analytic Framework . 13 1.2.3 Computational Models of Music/Composition .
    [Show full text]
  • The LOOPS Project (1982-1986)
    Programming Languges Programming Languages -- The LOOPS Project (1982-1986) Main Participants: Daniel Bobrow, Sanjay Mittal, Stanley Lanning, and Mark Stefik. The LOOPS (Lisp Object-Oriented Language) project was started to support development of expert systems project at PARC. We wanted a language that had many of the features of frame languages, such as objects, annotated values, inheritance, and attached procedures. We drew heavily on Smalltalk-80, which was being developed next door. Bobrow and Stefik had done frame languages before (KRL and UNITS, respectively). KRL was one of the first frame languges ever and established the paradigm. Units was part of a doctoral dissertation, was heavily used at Stanford, and was subsequently developed by Intellicorp to become KEE. Loops was a multiple-paradigm extension to Interlisp-D. It had ● Object-oriented programming. (Classes and objects, class variables, instance variables, methods, multiple-inheritance, interactive class browsers) ● Access-oriented programming. Nestable active values that can be attached to instance variables. Whenever a program puts a value to an instance variable or gets a value from an instance variable to which active values are attached, procedures specified in the active value are triggered. Active values also enabled attaching lists of property values to instance variables. This was used for creating audit trails and other things. ● Rule-oriented programming. A simple forward-chaining rule language with facilities for leaving an audit trail via active values. Loops provided "gauges" that could be used for debugging and for monitoring in simulation programs. Gauges were LOOPS objects. They could be attached to any value of any object in the system and provide a visual indication of program activity.
    [Show full text]
  • Common Lisp Object System
    Common Lisp Object System by Linda G. DeMichiel and Richard P. Gabriel Lucid, Inc. 707 Laurel Street Menlo Park, California 94025 (415)329-8400 [email protected] [email protected] with Major Contributions by Daniel Bobrow, Gregor Kiczales, and David Moon Abstract The Common Lisp Object System is an object-oriented system that is based on the concepts of generic functions, multiple inheritance, and method combination. All objects in the Object System are instances of classes that form an extension to the Common Lisp type system. The Common Lisp Object System is based on a meta-object protocol that renders it possible to alter the fundamental structure of the Object System itself. The Common Lisp Object System has been proposed as a standard for ANSI Common Lisp and has been tentatively endorsed by X3J13. Common Lisp Object System by Linda G. DeMichiel and Richard P. Gabriel with Major Contributions by Daniel Bobrow, Gregor Kiczales, and David Moon 1. History of the Common Lisp Object System The Common Lisp Object System is an object-oriented programming paradigm de- signed for Common Lisp. Over a period of eight months a group of five people, one from Symbolics and two each from Lucid and Xerox, took the best ideas from CommonLoops and Flavors, and combined them into a new object-oriented paradigm for Common Lisp. This combination is not simply a union: It is a new paradigm that is similar in its outward appearances to CommonLoops and Flavors, and it has been given a firmer underlying semantic basis. The Common Lisp Object System has been proposed as a standard for ANSI Common Lisp and has been tentatively endorsed by X3J13.
    [Show full text]
  • The Common Lisp Object System: an Overview
    The Common Lisp Object System: An Overview by Linda G. DeMichiel and Richard P. Gabriel Lucid, Inc. Menlo Park, California 1. Abstract The Common Lisp Object System is an object-oriented system that is based on the concepts of generic functions, multiple inheritance, and method combination. All objects in the Object System are instances of classes that form an extension to the Common Lisp type system. The Common Lisp Object System is based on a meta-object protocol that renders it possible to alter the fundamental structure of the Object System itself. The Common Lisp Object System has been proposed as a standard for ANSI Common Lisp and has been tentatively endorsed by X3J13. 2. History of the Common Lisp Object System The Common Lisp Object System is an object-oriented programming paradigm de- signed for Common Lisp. The lack of a standardized object-oriented extension for Common Lisp has long been regarded as a shortcoming by the Common Lisp community. Two sepa- rate and independent groups began work on an object-oriented extension to Common Lisp several years ago. One group is Symbolics, Inc. with New Flavors, and the other is Xerox PARC with CommonLoops. During the summer of 1986, these two groups met to explore combining their designs for submission to X3J13, a technical working group charged with producing an ANSI standard for Common Lisp. At the time of the exploratory meetings between Symbolics and Xerox, the authors of this paper became involved in the technical design work. The major participants in this effort were David Moon and Sonya Keene from Symbolics, Daniel Bobrow and Gregor Kiczales from Xerox, and Richard Gabriel and Linda DeMichiel from Lucid.
    [Show full text]
  • CMUCL User's Manual
    CMUCL User’s Manual Robert A. MacLachlan, Editor October 2010 20b CMUCL is a free, high-performance implementation of the Common Lisp programming lan- guage, which runs on most major Unix platforms. It mainly conforms to the ANSI Common Lisp Standard. CMUCL features a sophisticated native-code compiler, a foreign function interface, a graphical source-level debugger, an interface to the X11 Window System, and an Emacs-like edi- tor. Keywords: lisp, Common Lisp, manual, compiler, programming language implementation, pro- gramming environment This manual is based on CMU Technical Report CMU-CS-92-161, edited by Robert A. MacLachlan, dated July 1992. Contents 1 Introduction 1 1.1 Distribution and Support . 1 1.2 Command Line Options . 2 1.3 Credits . 3 2 Design Choices and Extensions 6 2.1 Data Types . 6 2.1.1 Integers . 6 2.1.2 Floats . 6 2.1.3 Extended Floats . 9 2.1.4 Characters . 10 2.1.5 Array Initialization . 10 2.1.6 Hash tables . 10 2.2 Default Interrupts for Lisp . 11 2.3 Implementation-Specific Packages . 12 2.4 Hierarchical Packages . 13 2.4.1 Introduction . 13 2.4.2 Relative Package Names . 13 2.4.3 Compatibility with ANSI Common Lisp . 14 2.5 Package Locks . 15 2.5.1 Rationale . 15 2.5.2 Disabling package locks . 16 2.6 The Editor . 16 2.7 Garbage Collection . 16 2.7.1 GC Parameters . 17 2.7.2 Generational GC . 18 2.7.3 Weak Pointers . 19 2.7.4 Finalization . 19 2.8 Describe . 19 2.9 The Inspector .
    [Show full text]
  • The Structure of a Programming Language
    The Structure of aProgramming Programming Richard P. Gabriel LanguageLanguage “I don’t want to die in a language IBM Research I can’t understand.” Redwood City, California USA RevolutionRevolution – Jorge Luis Borges us.ibm.com rpg@ {dreamsongs.com Abstract Engineering often precedes science. Incommensurability is real. Categories and Subject Descriptors A.0 [General] General Terms Design Keywords Engineering, science, paradigms, incommensu- rability t In 1990, two young and very smart computer sci- entists—Gilad Bracha and William Cook—wrote a pivotal paper called “Mixin-based Inheritance” [1], which immediately laid claim to being the first scientific paper on mixins. In that paper they described look- ing at Beta, Smalltalk, Flavors, and CLOS, and discovering a mechanism that could account for the three different sorts of inheritance found in these languages—including mixins from Flavors and CLOS. They named their new mechanism “mixins.” My attention was directed to this paper by Gilad Bracha himself when he told me in Brazil at AOSD in the spring of 2011 that most Lisp people who read the paper had strong objections to what he and William Cook had written about Lisp and CLOS. That night I pulled the paper down from the ACM server and read it while outside enormous puffed clouds dwelled overhead, lit from beneath by the town of Porto de Galinhas on the Brazilian coast; the smells of burning sugarcane and Engineering(,) A Path To Science bitter ocean pushed into my room. t Engineers build things; scientists describe reality; philoso- phers get lost in broad daylight. What I read in Brazil reminded me of my quest to dem- onstrate that in the pursuit of knowledge, at least in software and programming languages, engineering typically precedes Permission to make digital or hard copies of all or part of this work science—that is, even if science ultimately produces the most for personal or classroom use is granted without fee provided that reliable facts, the process often begins with engineering.
    [Show full text]
  • Method Combinators Didier Verna
    Method Combinators Didier Verna To cite this version: Didier Verna. Method Combinators. European Lisp Symposium, 2018, Marbella, Spain. hal- 01813488 HAL Id: hal-01813488 https://hal.archives-ouvertes.fr/hal-01813488 Submitted on 12 Jun 2018 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. Method Combinators Didier Verna EPITA Research and Development Laboratory Le Kremlin-Bicêtre, France [email protected] ABSTRACT 1 INTRODUCTION In traditional object-oriented languages, the dynamic dispatch al- Common Lisp was the rst programming language equipped with gorithm is hardwired: for every polymorphic call, only the most an object-oriented (OO) layer to be standardized [16]. Although specic method is used. Clos, the Common Lisp Object System, in the lineage of traditional class-based OO languages such as goes beyond the traditional approach by providing an abstraction Smalltalk and later C++ and Java, Clos, the Common Lisp Ob- known as method combinations: when several methods are applica- ject System [2, 5, 7, 9], departs from those in several important ble, it is possible to select several of them, decide in which order ways. they will be called, and how to combine their results, essentially First of all, Clos oers native support for multiple dispatch [3, 4].
    [Show full text]