DOCSLIB.ORG

Definition of a Type System for Generic and Reflective Graph

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Definition of a Type System for Generic and Reflective Graph Definition of a Type System for Generic and Reflective Graph Transformations Vom Fachbereich Elektrotechnik und Informationstechnik der Technischen Universitat¨ Darmstadt zur Erlangung des akademischen Grades eines Doktor-Ingenieurs (Dr.-Ing.) genehmigte Dissertation von Dipl.-Ing. Elodie Legros Geboren am 09.01.1982 in Vitry-le-Franc¸ois (Frankreich) Referent: Prof. Dr. rer. nat. Andy Schurr¨ Korreferent: Prof. Dr. Bernhard Westfechtel Tag der Einreichung: 17.12.2013 Tag der mundlichen¨ Prufung:¨ 30.06.2014 D17 Darmstadt 2014 Schriftliche Erklarung¨ Gemaߨ x9 der Promotionsordnung zur Erlangung des akademischen Grades eines Doktors der Ingenieurwissenschaften (Dr.-Ing.) der Technischen Uni- versitat¨ Darmstadt Ich versichere hiermit, dass ich die vorliegende Dissertation allein und nur unter Verwendung der angegebenen Literatur verfasst habe. Die Arbeit hat bisher noch nicht zu Prufungszwecken¨ gedient. Frederiksberg (Danemark),¨ den 17.12.2013 ..................................... Elodie Legros Acknowledgment My very special thanks go to my advisor, Prof. Dr. rer. nat. Andy Schurr,¨ who has supported me during all phases of this thesis. His many ideas and advices have been a great help in this work. He has always been available every time I had questions or wanted to discuss some points of my work. His patience in reviewing and proof-reading this thesis, especially after I left the TU Darmstadt and moved to Denmark, deserves my gratitude. I am fully convinced that I would not have been able to achieve this thesis without his unswerving support. For all this: thank you! Another person I am grateful to for his help is Prof. Dr. Bernhard Westfechtel. Reviewing a thesis is no easy task, and I want to thank him for having assumed this role and helped me in correcting details I missed in my work. I had the chance to work in a friendly atmosphere with very nice colleagues in the Real-Time Systems Lab at the TU Darmstadt. It helped me in persevering in the long journey this thesis has been, and I feel very thankful for it. I would like to address a special thank to Carsten Amelunxen and Felix Klar as co-writers of pub- lications. They helped me a lot in developing ideas, concept and examples which are now integrated in this thesis. I also want to thanks Martin Wieber, not only for the cooperation on the MAJA project, but also for having been such a kind and cheerful colleague. I also want to thank Dr. Ingo Sturmer,¨ Anna Trogel¨ and Jae-Won Choi (Model Engineering Solutions) for the collaboration in the MATE/MAJA projects, i.e. the context and motivation for my work. Speaking about the MAJA project, I am grate- ful to the Federal Ministry of Education and Research (BMBF) who supported this project by providing research funding. My thanks go to the Software Engineering Research Group Kassel for having been such a great help for all questions concerning the SDM graph transformations. I am grateful to the Technische Universitat¨ Darmstadt too for the research grants which allowed me to start this thesis. Finally, I want to thank my boyfriend for his patience each time I had to say “no” to a trip or just a walk because I had to work on my thesis. Last but not least, my parents deserve my gratitude for their patience and support. They heard the word “thesis” for so many years almost every time I called them, and every time they cheered me up. Merci a` tous les deux, Papa et Maman! Abstract This thesis presents the extension of the graph transformation language SDM (Story Driven Modeling) with generic and reflective features as well as the definition of type checking rules for this language. The generic and reflective features aim at improving the reusability and expressiveness of SDM, whereas the type checking rules will ensure the type-safety of graph transformations. This thesis starts with an explanation of the relevant concepts as well as a descrip- tion of the context in order to provide the reader with a better understanding of our approach. The model driven development of software, today considered as the standard paradigm, is generally based on the use of domain-specific languages such as MATLAB Simulink and Stateflow. To increase the quality, the reliabil- ity, and the efficiency of models and the generated code, checking and elimination of detected guideline violations defined in huge catalogues has become an essen- tial, but error-prone and time-consuming task in the development process. The MATE/MAJA projects, which are based on the use of the SDM language, aim at an automation of this task for MATLAB Simulink/Stateflow models. Modeling guidelines can be specified on a very high level of abstraction by means of graph transformations. Moreover, these specifications allow for the generation of guide- line checking tools. Unfortunately, most graph transformation languages do not offer appropriate concepts for reuse of specification fragments - a MUST, when we deal with hundreds of guidelines. As a consequence we present an extension of the SDM language which supports the definition of generic rewrite rules and combines them with the reflective programming mechanisms of Java and the model reposi- tory interface standard JMI. Reusability and expressiveness are not the only aspects we want to improve. An- other fundamental aspect of graph transformations must be ensured: their correct- ness in order to prevent type errors while executing the transformations. Checking and testing the graph transformations manually would ruin the benefit obtained by the automation of the guideline checking and by the generic and reflective features. Therefore, we propose in this work a type-checking method for graph transforma- tions. We introduce a new notation for rules of inference and define a type system for SDM. We also proposed an algorithm to apply this type system. We illustrate and evaluate both contributions of our work by applying them on run- ning examples. Proposals for other additional SDM features as well as for possible improvements of our type checking open new perspectives and future research to pursue our work. Keywords: Graph transformations, SDM, generic, reflective, type checking, rules of inference Zusammenfassung Diese Arbeit stellt die Erweiterung der Graphtransformationssprache SDM (Story Driven Modeling) mit generischen und reflektiven Features sowie die Definition eines Typsystems vor. Die generischen und reflektiven Features haben zum Ziel die Verbesserung der Wiederverwendung und Ausdrucksfahigkeit¨ von SDM, wahrend¨ die Ableitungsregeln (oder Inferenzregeln) des Typsystems die Typsicherheit der Graphtransformationen gewahrleisten.¨ Diese Dissertation fangt¨ mit einer Beschreibung der relevanten Begriffe sowie des Kontextes an, um dem Leser ein besseres Verstandnis¨ unseres Ansatzes´ zu ermit- teln. Die modellgetriebene Softwareentwicklung, die heutzutage als Standard gilt, basiert generell auf domainspezifischen Sprachen wie MATLAB Simulink und Stateflow. Um die Qualitat,¨ die Verlasslichkeit¨ und die Effizienz von Modellen und von dem generierten Code zu garantieren, sind die Uberpr¨ ufung¨ und die Behe- bung der verletzten Modellierungsrichtlinien eine notwendige, aber fehleranfallige¨ und zeitaufwandige,¨ Aufgabe wahrend¨ des Entwicklungsprozesses. Das Ziel der MATE/MAJA-Projekte, die auf der Verwendung der SDM-Transformationssprache basieren, ist die Automatisierung dieser Aufgabe fur¨ MATLAB Simulink/Stateflow Modelle. Die Modellierungsrichtlinien konnen¨ auf einem hohen Abstraktionsniveau mit Hilfe von Graphtransformationen spezifiziert werden. Diese Spezifikationen ermoglichen¨ dazu die Generierung von Werkzeugen zur Richtliniensanalyse. Lei- der bieten die meisten Graphtransformationssprachen die zur Wiederverwendung geeigneten Konzepte nicht an - ein MUSS, wenn man sich mit Hunderten von Richtlinien beschaftigt.¨ Deshalb stellen wir eine Erweiterung der SDM-Sprache, die die Spezifikation von generischen Graphersetzungsregeln unterstutzt,¨ und die diese mit den reflektiven Programmierungsmechanismen von Java und dem Stan- dard JMI kombiniert, vor. Wiederverwendung und Ausdrucksfahigkeit¨ sind nicht die einzigen Aspekte, die wir verbessern mochten.¨ Ein anderer wichtiger Aspekt der Graphtransformatio- nen muss gepruft¨ werden: ihre Korrektheit, um Typfehler bei der Ausfuhrung¨ der Transformationen zu unterdrucken.¨ Eine manuelle Uberpr¨ ufung¨ der Graphtrans- formationen wurde¨ den Vorteil der automatisierten Richtliniensanalyse und der generischen und reflektiven Features zunichte machen. Deshalb schlagen wir in dieser Arbeit einen Ansatz zur Typuberpr¨ ufung¨ von Graphtransformationen vor. Wir fuhren¨ eine neue Notation fur¨ die Inferenzregeln ein und definieren ein Typ- system fur¨ SDM. Wir veranschaulichen und evaluieren die beiden Beitrage,¨ indem wir diese auf konkreten Beispielen anwenden. Vorschlage¨ fur¨ weitere SDM-Features sowie mo-¨ gliche Verbesserungen von unserem Typsystem bieten Anregungen fur¨ kunftige¨ Arbeite an. Stichworter:¨ Graphtransformationen, SDM, Generizitat,¨ Reflektivitat,¨ Typsicher- heit, Inferenzregeln Contents 1 Introduction 15 1.1 Context and Motivation . 15 1.2 Contribution . 17 1.3 Overview . 19 2 Fundamentals 21 2.1 Meta-Object Facility and Java Metadata Interface . 21 2.1.1 Model Driven Engineering . 22 2.1.2 Meta Object Facilities . 23 2.1.3 Java Metadata Interface . 25 2.2 Model Transformations based on Graph Rewriting . 27 2.2.1 Model Transformations . 27 2.2.2 Graph Rewriting Systems . 29 2.3 MOSL . 32 2.3.1 MOSL Schema and Constraint Languages . 33 2.3.2 MOSL Transformation Language . 35 2.3.3
Load more

Recommended publications
  • Types and Programming Languages by Benjamin C
    < Free Open Study > . .Types and Programming Languages by Benjamin C. Pierce ISBN:0262162091 The MIT Press © 2002 (623 pages) This thorough type-systems reference examines theory, pragmatics, implementation, and more Table of Contents Types and Programming Languages Preface Chapter 1 - Introduction Chapter 2 - Mathematical Preliminaries Part I - Untyped Systems Chapter 3 - Untyped Arithmetic Expressions Chapter 4 - An ML Implementation of Arithmetic Expressions Chapter 5 - The Untyped Lambda-Calculus Chapter 6 - Nameless Representation of Terms Chapter 7 - An ML Implementation of the Lambda-Calculus Part II - Simple Types Chapter 8 - Typed Arithmetic Expressions Chapter 9 - Simply Typed Lambda-Calculus Chapter 10 - An ML Implementation of Simple Types Chapter 11 - Simple Extensions Chapter 12 - Normalization Chapter 13 - References Chapter 14 - Exceptions Part III - Subtyping Chapter 15 - Subtyping Chapter 16 - Metatheory of Subtyping Chapter 17 - An ML Implementation of Subtyping Chapter 18 - Case Study: Imperative Objects Chapter 19 - Case Study: Featherweight Java Part IV - Recursive Types Chapter 20 - Recursive Types Chapter 21 - Metatheory of Recursive Types Part V - Polymorphism Chapter 22 - Type Reconstruction Chapter 23 - Universal Types Chapter 24 - Existential Types Chapter 25 - An ML Implementation of System F Chapter 26 - Bounded Quantification Chapter 27 - Case Study: Imperative Objects, Redux Chapter 28 - Metatheory of Bounded Quantification Part VI - Higher-Order Systems Chapter 29 - Type Operators and Kinding Chapter 30 - Higher-Order Polymorphism Chapter 31 - Higher-Order Subtyping Chapter 32 - Case Study: Purely Functional Objects Part VII - Appendices Appendix A - Solutions to Selected Exercises Appendix B - Notational Conventions References Index List of Figures < Free Open Study > < Free Open Study > Back Cover A type system is a syntactic method for automatically checking the absence of certain erroneous behaviors by classifying program phrases according to the kinds of values they compute.
    [Show full text]
  • Functional Pls Introduction to Haskell
    Thoughts on Assignment 4 PL Category: Functional PLs Introduction to Haskell CS F331 Programming Languages CSCE A331 Programming Language Concepts Lecture Slides Friday, February 22, 2019 Glenn G. Chappell Department of Computer Science University of Alaska Fairbanks [email protected] © 2017–2019 Glenn G. Chappell Thoughts on Assignment 4 Introduction In Assignment 4 you will be writing a Recursive-Descent parser, in the form of Lua module parseit. It will be similar to module rdparser4 (written in class), but it will involve a different grammar & AST specification. In Assignment 6 you will write an interpreter that takes, as input, an AST of the form your parser returns. The result will be an implementation of a programming language called Jerboa. Module parseit is to parse a complete programming language, while module rdparser4 only parses expressions. Nonetheless, Jerboa has expressions, and they work in much the same way as those handled by rdparser4. I suggest using file rdparser4.lua as a starting point for Assignment 4. 22 Feb 2019 CS F331 / CSCE A331 Spring 2019 2 Thoughts on Assignment 4 The Goal Here is a sample Jerboa program, again. # Function fibo # Main Program # Given k, return F(k), where # F(n) = nth Fibonacci no. # Get number of Fibos to output def fibo() write("How many Fibos to print? ") a = 0 # Consecutive Fibos n = readnum() b = 1 write(cr) i = 0 # Loop counter while i < k # Print requested number of Fibos c = a+b # Advance j = 0 # Loop counter a = b while j < n b = c k = j i = i+1 # ++counter write("F(",j,")
    [Show full text]
  • Comparison of Programming Languages
    ECE326 PROGRAMMING LANGUAGES Lecture 1 : Course Introduction Kuei (Jack) Sun ECE University of Toronto Fall 2019 Course Instructor Kuei (Jack) Sun Contact Information Use Piazza Send me (Kuei Sun) a private post Not “Instructors”, otherwise the TAs will also see it http://piazza.com/utoronto.ca/fall2019/ece326 Sign up to the course to get access Office: PRA371 (office hours upon request only) Research Interests Systems programming, software optimization, etc. 2 Course Information Course Website http://fs.csl.toronto.edu/~sunk/ece326.html Lecture notes, tutorial slides, assignment handouts Quercus Grade posting, course evaluation, lab group sign-up! Piazza Course announcement, course discussion Assignment discussion Lab TAs will read and answer relevant posts periodically 3 Course Information No required textbook Exam questions will come from lectures, tutorials, and assignments See course website for suggested textbooks Lab sessions Get face-to-face help from a TA with your assignments Tutorials Cover supplementary materials not in lectures Go through sample problems that may appear on exams 4 Volunteer Notetakers Help your peers Improve your own notetaking skills Receive Certificate of Recognition Information: https://www.studentlife.utoronto.ca/as/note-taking Registration: https://clockwork.studentlife.utoronto.ca/custom/misc/home.aspx Notetakers needed for lectures and tutorials 5 Background Programming Languages A formal language consisting of a instructions to implement algorithms and perform
    [Show full text]
  • Analytická Řešení Vybraných Typů Diferenciálních Rovnic
    VYSOKÉ UČENÍ TECHNICKÉ V BRNĚ BRNO UNIVERSITY OF TECHNOLOGY FAKULTA STROJNÍHO INŽENÝRSTVÍ FACULTY OF MECHANICAL ENGINEERING ÚSTAV AUTOMATIZACE A INFORMATIKY INSTITUTE OF AUTOMATION AND COMPUTER SCIENCE ANALYTICKÁ ŘEŠENÍ VYBRANÝCH TYPŮ DIFERENCIÁLNÍCH ROVNIC: SOFTWAROVÁ PODPORA PRO STUDENTY TECHNICKÝCH OBORŮ ANALYTICAL SOLUTIONS FOR SELECTED TYPES OF DIFFERENTIAL EQUATIONS: SOFTWARE SUPPORT TOOL FOR STUDENTS IN TECHNICAL FIELDS BAKALÁŘSKÁ PRÁCE BACHELOR'S THESIS AUTOR PRÁCE Daniel Neuwirth, DiS. AUTHOR VEDOUCÍ PRÁCE Ing. Jan Roupec, Ph.D. SUPERVISOR BRNO 2017 ABSTRAKT Cílem této práce bylo vytvořit počítačovou aplikaci s jednoduchým uživatelským rozhraním, určenou pro řešení vybraných typů diferenciálních rovnic, jejíž výstup není omezen na prosté zobrazení konečného výsledku, nýbrž zahrnuje i kompletní postup výpočtu, a díky tomu může sloužit jako podpůrná výuková pomůcka pro studenty vysokých škol. ABSTRACT The aim of this thesis was to create a computer application with a simple user interface for solving selected types of differential equations, whose output is not limited to display a final result only, but also includes a complete calculation procedure and therefore can serve as a supportive teaching aid for university students. KLÍČOVÁ SLOVA diferenciální rovnice, počítačový algebraický systém, programovací jazyk C++ KEYWORDS differential equation, computer algebra system, C++ programming language BIBLIOGRAFICKÁ CITACE NEUWIRTH, Daniel. Analytická řešení vybraných typů diferenciálních rovnic: softwarová podpora pro studenty technických oborů. Brno: Vysoké učení technické v Brně, Fakulta strojního inženýrství, 2017. 77 s. Vedoucí bakalářské práce Ing. Jan Roupec, Ph.D. PODĚKOVÁNÍ Rád bych poděkoval vedoucímu své bakalářské práce Ing. Janu Roupcovi, Ph.D. za odborné vedení při tvorbě této práce, za cenné rady a návrhy ke zlepšení, drobné korektury a zejména za jeho entuziasmus, se kterým k tomuto procesu přistupoval.
    [Show full text]
  • 4500/6500 Programming Languages What Are Types? Different Definitions
    What are Types? ! Denotational: Collection of values from domain CSCI: 4500/6500 Programming » integers, doubles, characters ! Abstraction: Collection of operations that can be Languages applied to entities of that type ! Structural: Internal structure of a bunch of data, described down to the level of a small set of Types fundamental types ! Implementers: Equivalence classes 1 Maria Hybinette, UGA Maria Hybinette, UGA 2 Different Definitions: Types versus Typeless What are types good for? ! Documentation: Type for specific purposes documents 1. "Typed" or not depends on how the interpretation of the program data representations is determined » Example: Person, BankAccount, Window, Dictionary » When an operator is applied to data objects, the ! Safety: Values are used consistent with their types. interpretation of their values could be determined either by the operator or by the data objects themselves » Limit valid set of operation » Languages in which the interpretation of a data object is » Type Checking: Prevents meaningless operations (or determined by the operator applied to it are called catch enough information to be useful) typeless languages; ! Efficiency: Exploit additional information » those in which the interpretation is determined by the » Example: a type may dictate alignment at at a multiple data object itself are called typed languages. of 4, the compiler may be able to use more efficient 2. Sometimes it just means that the object does not need machine code instructions to be explicitly declared (Visual Basic, Jscript
    [Show full text]
  • Sqlite 1 Sqlite
    SQLite 1 SQLite SQLite Developer(s) D. Richard Hipp Initial release August 2000 [1] Latest stable 3.8.4.2 (March 26, 2014) [±] Written in C Operating system Cross-platform Size 658 KiB Type RDBMS (embedded) License Public domain [2] Website sqlite.org SQLite (/ˌɛskjuːɛlˈlaɪt/ or /ˈsiːkwəl.laɪt/) is a relational database management system contained in a C programming library. In contrast to other database management systems, SQLite is not a separate process that is accessed from the client application, but an integral part of it. SQLite is ACID-compliant and implements most of the SQL standard, using a dynamically and weakly typed SQL syntax that does not guarantee the domain integrity. SQLite is a popular choice as embedded database for local/client storage in application software such as web browsers. It is arguably the most widely deployed database engine, as it is used today by several widespread browsers, operating systems, and embedded systems, among others. SQLite has many bindings to programming languages. The source code for SQLite is in the public domain. Design Unlike client–server database management systems, the SQLite engine has no standalone processes with which the application program communicates. Instead, the SQLite library is linked in and thus becomes an integral part of the application program. (In this, SQLite follows the precedent of Informix SE of c. 1984 [3]) The library can also be called dynamically. The application program uses SQLite's functionality through simple function calls, which reduce latency in database access: function calls within a single process are more efficient than inter-process communication.
    [Show full text]
  • Gradual Security Typing with References
    2013 IEEE 26th Computer Security Foundations Symposium Gradual Security Typing with References Luminous Fennell, Peter Thiemann Dept. of Computing Science University of Freiburg Freiburg, Germany Email: {fennell, thiemann}@informatik.uni-freiburg.de Abstract—Type systems for information-flow control (IFC) The typing community studies a similar interplay between are often inflexible and too conservative. On the other hand, static and dynamic checking. Gradual typing [25], [26] is dynamic run-time monitoring of information flow is flexible and an approach where explicit cast operations mediate between permissive but it is difficult to guarantee robust behavior of a program. Gradual typing for IFC enables the programmer to coexisting statically and dynamically typed program frag- choose between permissive dynamic checking and a predictable, ments. The type of a cast operation reflects the outcome of conservative static type system, where needed. the run-time test performed by the cast: The return type of We propose ML-GS, a monomorphic ML core language with the cast is the compile-time manifestation of the positive test; references and higher-order functions that implements gradual a negative outcome of the test causes a run-time exception. typing for IFC. This language contains security casts, which enable the programmer to transition back and forth between Disney and Flanagan propose an integration of security static and dynamic checking. types with dynamic monitoring via gradual typing [11]. Such In particular, ML-GS enables non-trivial casts on reference an integration enables the stepwise introduction of checked types so that a reference can be safely used everywhere in a security policies into a software system.
    [Show full text]
  • PL Category: Functional Pls Introduction to Haskell
    PL Category: Functional PLs Introduction to Haskell CS F331 Programming Languages CSCE A331 Programming Language Concepts Lecture Slides Friday, February 21, 2020 Glenn G. Chappell Department of Computer Science University of Alaska Fairbanks [email protected] © 2017–2020 Glenn G. Chappell Review 2020-02-21 CS F331 / CSCE A331 Spring 2020 2 Review Overview of Lexing & Parsing Parsing Lexer Parser Character Lexeme AST or Stream Stream Error return (*dp + 2.6); //x return (*dp + 2.6); //x returnStmt key op id op num binOp: + lit punct punct unOp: * numLit: 2.6 Two phases: id: dp § Lexical analysis (lexing) § Syntax analysis (parsing) The output of a parser is typically an abstract syntax tree (AST). Specifications of these will vary. 2020-02-21 CS F331 / CSCE A331 Spring 2020 3 Review The Basics of Syntax Analysis — Categories of Parsers Parsing methods can be divided into two broad categories. Top-Down Parsers § Go through derivation top to bottom, expanding nonterminals. § Important subcategory: LL parsers (read input Left-to-right, produce Leftmost derivation). § Often hand-coded—but not always. § Method we look at: Predictive Recursive Descent. Bottom-Up Parsers § Go through the derivation bottom to top, reducing substrings to nonterminals. § Important subcategory: LR parsers (read input Left-to-right, produce Rightmost derivation). § Almost always automatically generated. § Method we look at: Shift-Reduce. 2020-02-21 CS F331 / CSCE A331 Spring 2020 4 Review Parsing Wrap-Up — Efficiency of Parsing Counting the input size as the number of lexemes/characters: Practical parsers (and lexers) run in linear time. This includes state-machine lexers, Predictive Recursive-Descent parsers and Shift-Reduce parsers.
    [Show full text]
  • Advanced Programming Principles CM20214
    In code bigclass x = new bigclass(1); x = new bigclass(2); or (setq x (make <bigclass> 1)) (setq x (make <bigclass> 2)) the memory allocated to the new class 1 is no longer accessible to the program It is garbage, so we need a garbage collector to search out inaccessible memory and reclaim it for the system GC Some languages have Garbage Collection, some don’t 1 / 214 It is garbage, so we need a garbage collector to search out inaccessible memory and reclaim it for the system GC Some languages have Garbage Collection, some don’t In code bigclass x = new bigclass(1); x = new bigclass(2); or (setq x (make <bigclass> 1)) (setq x (make <bigclass> 2)) the memory allocated to the new class 1 is no longer accessible to the program 2 / 214 GC Some languages have Garbage Collection, some don’t In code bigclass x = new bigclass(1); x = new bigclass(2); or (setq x (make <bigclass> 1)) (setq x (make <bigclass> 2)) the memory allocated to the new class 1 is no longer accessible to the program It is garbage, so we need a garbage collector to search out inaccessible memory and reclaim it for the system 3 / 214 Languages without integral GC include C, C++ In languages without GC, if you drop all references to an object, that’s the programmer’s problem The Java-like code above is also valid C++ Thus it is buggy C++ with a memory leak GC Languages with integral GC include Lisp, Haskell, Java, Perl 4 / 214 In languages without GC, if you drop all references to an object, that’s the programmer’s problem The Java-like code above is also valid C++ Thus it
    [Show full text]
  • The C++ Programming Language in Modern Computer Science
    Shayan Shajarian THE C++ PROGRAMMING LANGUAGE IN MODERN COMPUTER SCIENCE Faculty of Information Technology and Communication Sciences (ITC) Master of Science Thesis April 2020 1 ABSTRACT Shayan Shajarian: The C++ programming language in modern computer science Master of science thesis Tampere University Information Technology April 2020 This thesis has studied the C++ programming language’s usefulness in modern computer science both in suitability for developers and education by overviewing its history and main features and comparing it to its main alternatives. The research was mainly conducted with literature reviews and methods used for studying the subject where both quantitative in form of performance analysis and qualitative in the form of analysis of non-numeric attributes. This thesis has found that the C++ programming language is a very capable programming language for overall development, but the language’s popularity has shifted towards system-level programming while the language is losing popularity for higher-level applications. The C++ programming language is also quite complex, making it too difficult to learn for beginners. Despite the complexity, the C++ programming language remains a very good language in terms of education for students of computer science because the language gives a good overview of programming as a whole. Keywords: C++, computer science, software production, education of programming The originality of this thesis has been checked using the Turnitin OriginalityCheck service. 2 TIIVISTELMÄ Shayan Shajarian: The C++ programming language in modern computer science Diplomityö Tampereen yliopisto Ohjelmistotuotanto Huhtikuu 2020 Tämä diplomityö on tutkinut C++-ohjelmointikielen hyödyllisyyttä sekä modernissa ohjelmistotuotannossa, että työkaluna tietotekniikan ja ohjelmoinnin opetukseen. Tutkimus suoritettiin tutkimalla C++-ohjelmointikielen historiaa, kielen yleisiä ominaisuuksia ja vertailemalla sitä muihin ohjelmointikieliin.
    [Show full text]
  • Pluggable, Iterative Type Checking for Dynamic Programming Languages
    Pluggable, Iterative Type Checking for Dynamic Programming Languages Tristan Allwood ([email protected]) Professor Susan Eisenbach (supervisor) Dr. Sophia Drossopoulou (second marker) University of London Imperial College of Science, Technology and Medicine Department of Computing Copyright c Tristan Allwood, 2006 Project sources available at: /homes/toa02/project/fleece/ June 13, 2006 Abstract Dynamically typed programming languages are great. They can be highly expressive, incredibly flexible, and very powerful. They free a programmer of the chains of needing to explicitly say what classes are allowed in any particular point in the program. They delay dealing with errors until the last possible moment at runtime. They trust the programmer to get the code right. Unfortunately, programmers are not to be trusted to get the code right! So to combat this, programmers started writing tests to exercise their code. The particularly conscientious ones started writing the tests before the code existed. The problem is, tests are still code, and tests would still only point out errors at runtime. Of course, some of these errors would be silly mistakes, e.g. misspelled local variables; some would be slightly more complicated, but a person reading the code could notice them. They are errors that could be detected while a program was being written. Static type systems could help detect these mistakes while the programs were being written. Retrofitting a mandatory static type system onto a dynamically typed programming language would not be a popular action, so instead the idea of optional and then pluggable type systems was raised. Here the type systems can be applied to the language, but they don’t have to be.
    [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]