Axiomatic Foundations and Algorithms for Deciding Semantic Equivalences of SQL Queries

Total Page:16

File Type:pdf, Size:1020Kb

Axiomatic Foundations and Algorithms for Deciding Semantic Equivalences of SQL Queries Axiomatic Foundations and Algorithms for Deciding Semantic Equivalences of SQL Queries Shumo Chu, Brendan Murphy, Jared Roesch, Alvin Cheung, Dan Suciu Paul G. Allen School of Computer Science and Engineering University of Washington fchushumo, jroesch, akcheung, [email protected], [email protected] ABSTRACT In the past, query optimizers were developed by only small num- Deciding the equivalence of SQL queries is a fundamental prob- ber of commercial database vendors with dedicated teams to handle lem in data management. As prior work has mainly focused on customer reported bugs. Such teams effectively acted as “manual studying the theoretical limitations of the problem, very few im- solvers” for query equivalences. The explosive growth of new data plementations for checking such equivalences exist. In this pa- analytic systems in recent decades (e.g., Spark SQL [12], Hive [4], per, we present a new formalism and implementation for reason- Dremel [42], Myria [39, 55], among many others) has unfortu- ing about the equivalences of SQL queries. Our formalism, U- nately exacerbated this problem significantly, as many such new semiring, extends SQL’s semiring semantics with unbounded sum- systems are developed by teams that simply lack the dedicated re- mation and duplicate elimination. U-semiring is defined using only sources to check every single rewrite implemented in their system. very few axioms and can thus be easily implemented using proof For example, the Calcite open source query processing engine [1] assistants such as Lean for automated query reasoning. Yet, they is mainly developed by open-source contributors. While it con- are sufficient enough to enable us reason about sophisticated SQL tains more than 232 rewrite rules in its optimization engine, none queries that are evaluated over bags and sets, along with various in- of which has been formally validated. The same holds true for sim- tegrity constraints. To evaluate the effectiveness of U-semiring, we ilar engines. have used it to formally verify 68 equivalent queries and rewrite On the other hand, deciding whether two arbitrary SQL queries rules from both classical data management research papers and are semantically equivalent is a well-studied problem in the data real-world SQL engines, where many of them have never been management research community that has shown to be undecid- proven correct before. able in general [11]. Most subsequent research has been directed at identifying fragments of SQL where equivalence is decidable, PVLDB Reference Format: under set semantics [17, 47] or bag semantics [24]. This line of Shumo Chu, Brendan Murphy, Jared Roesch, Alvin Cheung, Dan Suciu. work, focused on theoretical aspects of the problem [51, 47, 41], Axiomatic Foundations and Algorithms for Deciding Semantic Equivalences led to very few implementations, most of which were restricted to of SQL Queries. PVLDB, 11 (11): 1482-1495, 2018. DOI: https://doi.org/10.14778/3236187.3236200 applying the chase procedure to conjunctive queries [14]. An alternative approach to query equivalence was recently pro- posed by the COSETTE system [23] based on a new SQL seman- 1. INTRODUCTION tics. It interprets SQL relations as K-relations [35]. A K-relation All modern relational database management systems (DBMSs) is semiring that maps each tuple t to a value R(t) that denotes the contain a query optimizer that chooses the best means to execute multiplicity of the tuple in the relation. Normally, the multiplicity an input query. At the heart of an optimizer is a rule-based rewrite is an integer, thus the semiring K is the semiring of natural num- system that uses rewrite rules to transform the input SQL query bers N, but in order to support some of the SQL constructs (such as into another (hopefully more efficient) query to execute. A key projections, with or without DISTINCT), COSETTE resorts to using challenge in query optimization is how to ensure that the rewrit- a much more complex semiring, namely that of all univalent types ten query is indeed semantically equivalent to the input, i.e., that in Homotopy Type Theory (HoTT) [50]. Equivalence of two SQL the original and rewritten queries return the same results when exe- queries is then proven in COSETTE using the Coq proof assistant cuted on all possible input database instances. History suggests that extended with the HoTT library [36]. While the system can han- the lack of tools to establish such equivalences has caused long- dle many features of SQL, its reliance on HoTT makes it difficult standing, latent bugs in major database systems [32], and new bugs to extend as HoTT is both a Coq library under development and continue to arise [7, 10]. All such errors lead to incorrect results an active research area itself. As a result, COSETTE has a number returned that can cause dire consequences. of shortcomings. For example, COSETTE does not support foreign Permission to make digital or hard copies of all or part of this work for keys as they are difficult to model using the HoTT library in Coq. personal or classroom use is granted without fee provided that copies are In this paper, we propose a new algebraic structure, called the not made or distributed for profit or commercial advantage and that copies unbounded semiring, or U-semiring. We define the U-semiring bear this notice and the full citation on the first page. To copy otherwise, to by extending the standard commutative semiring with a few sim- republish, to post on servers or to redistribute to lists, requires prior specific ple constructs and axioms. This new algebraic structure serves as permission and/or a fee. Articles from this volume were invited to present their results at The 44th International Conference on Very Large Data Bases, a foundation for our new formalism that models the semantics of August 2018, Rio de Janeiro, Brazil. SQL. To prove the semantic equivalence of two SQL queries, we Proceedings of the VLDB Endowment, Vol. 11, No. 11 first convert them into U-semiring expressions, i.e., U-expressions. Copyright 2018 VLDB Endowment 2150-8097/18/07. Deciding the equivalence of queries then becomes determining the DOI: https://doi.org/10.14778/3236187.3236200 1482 equivalence of two U-expressions which, as we will show, is much Equivalent SQL Queries easier compared to classical approaches. SELECT*FROMRtWHERE t.a >= 12-- Q1 Our core contribution is identifying the minimal set of axioms for SELECT t2.*FROM I t1, R t2-- Q2 U-semirings that are sufficient to prove sophisticated SQL query WHERE t1.k = t2.kAND t1.a >= 12 equivalences. This is important as the number of axioms deter- mines the size of the trusted code base in any proof system. As where k is a key of R, and I is an index on R defined as: we will see, the few axioms we designed for U-semirings are sur- I :=SELECT t3.kAS k, t3.aASaFROM R t3 prisingly simple as they are just identities between two U-expres- Corresponding Equivalence in Semirings sions. Yet, they are sufficient to prove various advanced query op- timization rules that arise in real-world optimizers. Furthermore, Q1(t) = λ t: R (t) × [t:a ≥ 12] J XK we show how integrity constraints (ICs) such as keys and foreign Q2(t) = λ t: [t2 = t] × [t1:k = t2:k] × [t1:a ≥ 12]× keys can be expressed as U-expressions identities as well, and this t1;t2;t3 leads to a single framework that can model many different features [t3:k = t1:k] × [t3:a = t1:a] × R (t3) × R (t2) of SQL and the relational data model. This allows us to devise dif- J K J K ferent algorithms for deciding the equivalences of various types of Figure 1: Proving that a query is equivalent to a rewrite using SQL queries including those that involve views, or leverage ICs to an index I requires proving a subtle identity in a semiring. rewrite the input SQL query as part of the proof. To that end, we have developed a new algorithm, UDP, to au- that this algorithm is sound for general SQL queries and is com- tomatically decide the equivalence of two arbitrary SQL queries plete for Unions of Conjunctive Queries under set and bag se- that are evaluated under mixed set/bag semantics,1 and also in the mantics (Sec. 5). presence of indexes, views, and other ICs. At a high level, our • We have implemented UDP using the Lean proof assistant, and algorithm performs rewrites reminiscent to the chase/back-chase have evaluated UDP by collecting 69 real-world rewrite rules as procedure [45] but uses U-expressions rather than first order logic benchmarks, both from prior research work done in the database sentences. It performs a number of tests for isomorphisms or homo- research community, and from Apache Calcite [1], an open-source morphisms to capture the mixed set/bag semantics of SQL. Our al- relational query optimizer. To our knowledge, the majority of gorithm is sound in general and is complete in two restricted cases: these rules have been never proven correct before, while UDP can when the two queries are Unions of Conjunctive Queries (UCQ) automatically prove 62 of 68 correct ones and fail as intended on under set semantics, or UCQ under bag semantics. We implement the 1 buggy one (Sec. 6). UDP on top of the Lean proof assistant [26]. The implementation includes the modeling of relations and queries as U-expressions, axiomatic representations of ICs as simple U-expression identities, 2. OVERVIEW and the algorithm for checking the equivalence of U-expressions. We motivate our new semantics using an example query rewrite. We evaluate UDP using various optimization rules from classi- As shown in Fig.
Recommended publications
  • An Array-Oriented Language with Static Rank Polymorphism
    An array-oriented language with static rank polymorphism Justin Slepak, Olin Shivers, and Panagiotis Manolios Northeastern University fjrslepak,shivers,[email protected] Abstract. The array-computational model pioneered by Iverson's lan- guages APL and J offers a simple and expressive solution to the \von Neumann bottleneck." It includes a form of rank, or dimensional, poly- morphism, which renders much of a program's control structure im- plicit by lifting base operators to higher-dimensional array structures. We present the first formal semantics for this model, along with the first static type system that captures the full power of the core language. The formal dynamic semantics of our core language, Remora, illuminates several of the murkier corners of the model. This allows us to resolve some of the model's ad hoc elements in more general, regular ways. Among these, we can generalise the model from SIMD to MIMD computations, by extending the semantics to permit functions to be lifted to higher- dimensional arrays in the same way as their arguments. Our static semantics, a dependent type system of carefully restricted power, is capable of describing array computations whose dimensions cannot be determined statically. The type-checking problem is decidable and the type system is accompanied by the usual soundness theorems. Our type system's principal contribution is that it serves to extract the implicit control structure that provides so much of the language's expres- sive power, making this structure explicitly apparent at compile time. 1 The Promise of Rank Polymorphism Behind every interesting programming language is an interesting model of com- putation.
    [Show full text]
  • Compendium of Technical White Papers
    COMPENDIUM OF TECHNICAL WHITE PAPERS Compendium of Technical White Papers from Kx Technical Whitepaper Contents Machine Learning 1. Machine Learning in kdb+: kNN classification and pattern recognition with q ................................ 2 2. An Introduction to Neural Networks with kdb+ .......................................................................... 16 Development Insight 3. Compression in kdb+ ................................................................................................................. 36 4. Kdb+ and Websockets ............................................................................................................... 52 5. C API for kdb+ ............................................................................................................................ 76 6. Efficient Use of Adverbs ........................................................................................................... 112 Optimization Techniques 7. Multi-threading in kdb+: Performance Optimizations and Use Cases ......................................... 134 8. Kdb+ tick Profiling for Throughput Optimization ....................................................................... 152 9. Columnar Database and Query Optimization ............................................................................ 166 Solutions 10. Multi-Partitioned kdb+ Databases: An Equity Options Case Study ............................................. 192 11. Surveillance Technologies to Effectively Monitor Algo and High Frequency Trading ..................
    [Show full text]
  • Application and Interpretation
    Programming Languages: Application and Interpretation Shriram Krishnamurthi Brown University Copyright c 2003, Shriram Krishnamurthi This work is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 United States License. If you create a derivative work, please include the version information below in your attribution. This book is available free-of-cost from the author’s Web site. This version was generated on 2007-04-26. ii Preface The book is the textbook for the programming languages course at Brown University, which is taken pri- marily by third and fourth year undergraduates and beginning graduate (both MS and PhD) students. It seems very accessible to smart second year students too, and indeed those are some of my most successful students. The book has been used at over a dozen other universities as a primary or secondary text. The book’s material is worth one undergraduate course worth of credit. This book is the fruit of a vision for teaching programming languages by integrating the “two cultures” that have evolved in its pedagogy. One culture is based on interpreters, while the other emphasizes a survey of languages. Each approach has significant advantages but also huge drawbacks. The interpreter method writes programs to learn concepts, and has its heart the fundamental belief that by teaching the computer to execute a concept we more thoroughly learn it ourselves. While this reasoning is internally consistent, it fails to recognize that understanding definitions does not imply we understand consequences of those definitions. For instance, the difference between strict and lazy evaluation, or between static and dynamic scope, is only a few lines of interpreter code, but the consequences of these choices is enormous.
    [Show full text]
  • Handout 16: J Dictionary
    J Dictionary Roger K.W. Hui Kenneth E. Iverson Copyright © 1991-2002 Jsoftware Inc. All Rights Reserved. Last updated: 2002-09-10 www.jsoftware.com . Table of Contents 1 Introduction 2 Mnemonics 3 Ambivalence 4 Verbs and Adverbs 5 Punctuation 6 Forks 7 Programs 8 Bond Conjunction 9 Atop Conjunction 10 Vocabulary 11 Housekeeping 12 Power and Inverse 13 Reading and Writing 14 Format 15 Partitions 16 Defined Adverbs 17 Word Formation 18 Names and Displays 19 Explicit Definition 20 Tacit Equivalents 21 Rank 22 Gerund and Agenda 23 Recursion 24 Iteration 25 Trains 26 Permutations 27 Linear Functions 28 Obverse and Under 29 Identity Functions and Neutrals 30 Secondaries 31 Sample Topics 32 Spelling 33 Alphabet and Numbers 34 Grammar 35 Function Tables 36 Bordering a Table 37 Tables (Letter Frequency) 38 Tables 39 Classification 40 Disjoint Classification (Graphs) 41 Classification I 42 Classification II 43 Sorting 44 Compositions I 45 Compositions II 46 Junctions 47 Partitions I 48 Partitions II 49 Geometry 50 Symbolic Functions 51 Directed Graphs 52 Closure 53 Distance 54 Polynomials 55 Polynomials (Continued) 56 Polynomials in Terms of Roots 57 Polynomial Roots I 58 Polynomial Roots II 59 Polynomials: Stopes 60 Dictionary 61 I. Alphabet and Words 62 II. Grammar 63 A. Nouns 64 B. Verbs 65 C. Adverbs and Conjunctions 66 D. Comparatives 67 E. Parsing and Execution 68 F. Trains 69 G. Extended and Rational Arithmeti 70 H. Frets and Scripts 71 I. Locatives 72 J. Errors and Suspensions 73 III. Definitions 74 Vocabulary 75 = Self-Classify - Equal 76 =. Is (Local) 77 < Box - Less Than 78 <.
    [Show full text]
  • A Guide to PL/M Programming
    INTEL CORP. 3065 Bowers Avenue, Santa Clara, California 95051 • (408) 246-7501 mcs=a A Guide to PL/M programming PL/M is a new high level programming language designed specifically for Intel's 8 bit microcomputers. The new language gives the microcomputer systems program­ mer the same advantages of high level language programming currently available in the mini and large computer fields. Designed to meet the special needs of systems programming, the new language will drastically cut microcomputer programming time and costs without sacrifice of program efficiency. in addition, training, docu­ mentation, program maintenance and the inclusion of library subroutines will all be made correspondingly easier. PL/M is well suited for all microcomputer program­ ming applications, retaining the control and efficiency of assembly language, while greatly reducing programming effort The PL/M compiler is written in ANSI stand­ ard Fortran I V and thus will execute on most machines without alteration. SEPTEMBER 1973 REV.1 © Intel Corporation 1973 TABLE OF CONTENTS Section Page I. INTRODUCTION TO PL/M 1 II. A TUTORIAL APPROACH TO PL/M ............................ 2 1. The Organization of a PL/M Program ........................ 2 2. Basic Constituents of a PL/M Program ....................... 4 2.1. PL/M Character Set ................................ 4 2.2. Identifiers and Reserved Words ....................... 5 2.3. Comments . 7 3. PL/M Statement Organization . 7 4. PL/M Data Elements . 9 4.1. Variable Declarations ............................... 9 4.2. Byte and Double Byte Constants. .. 10 5. Well-Formed Expressions and Assignments . 11 6. A Simple Example. 15 7. DO-Groups. 16 7.1. The DO-WHILE Group ...........
    [Show full text]
  • Visual Programming Language for Tacit Subset of J Programming Language
    Visual Programming Language for Tacit Subset of J Programming Language Nouman Tariq Dissertation 2013 Erasmus Mundus MSc in Dependable Software Systems Department of Computer Science National University of Ireland, Maynooth Co. Kildare, Ireland A dissertation submitted in partial fulfilment of the requirements for the Erasmus Mundus MSc Dependable Software Systems Head of Department : Dr Adam Winstanley Supervisor : Professor Ronan Reilly June 30, 2013 Declaration I hereby certify that this material, which I now submit for assessment on the program of study leading to the award of Master of Science in Dependable Software Systems, is entirely my own work and has not been taken from the work of others save and to the extent that such work has been cited and acknowledged within the text of my work. Signed:___________________________ Date:___________________________ Abstract Visual programming is the idea of using graphical icons to create programs. I take a look at available solutions and challenges facing visual languages. Keeping these challenges in mind, I measure the suitability of Blockly and highlight the advantages of using Blockly for creating a visual programming environment for the J programming language. Blockly is an open source general purpose visual programming language designed by Google which provides a wide range of features and is meant to be customized to the user’s needs. I also discuss features of the J programming language that make it suitable for use in visual programming language. The result is a visual programming environment for the tacit subset of the J programming language. Table of Contents Introduction ............................................................................................................................................ 7 Problem Statement ............................................................................................................................. 7 Motivation..........................................................................................................................................
    [Show full text]
  • Frederick Phillips Brooks, Jr
    Frederick Phillips Brooks, Jr. Biography Frederick P. Brooks, Jr., was born in 1931 in Durham NC, and grew up in Greenville NC. He received an A.B. summa cum laude in physics from Duke and a Ph.D. in computer science from Harvard, under Howard Aiken, the inventor of the early Harvard computers. He joined IBM, working in Poughkeepsie and Yorktown, NY, 1956-1965. He was an architect of the Stretch and Harvest computers and then was the project manager for the development of IBM's System/360 family of computers and then of the Operating System/360 software. For this work he received a National Medal of Technology jointly with Bob O. Evans and Erich Bloch Brooks and Dura Sweeney in 1957 patented an interrupt system for the IBM Stretch computer that introduced most features of today's interrupt systems. He coined the term computer architecture. His System/360 team first achieved strict compatibility, upward and downward, in a computer family. His early concern for word processing led to his selection of the 8-bit byte and the lowercase alphabet for the System/360, engineering of many new 8-bit input/output devices, and introduction of a character-string datatype in the PL/I programming language. In 1964 he founded the Computer Science Department at the University of North Carolina at Chapel Hill and chaired it for 20 years. Currently, he is Kenan Professor of Computer Science. His principal research is in real-time, three-dimensional, computer graphics—“virtual reality.” His research has helped biochemists solve the structure of complex molecules and enabled architects to “walk through” structures still being designed.
    [Show full text]
  • Symantec™ Endpoint Protection 14.X for Linux Client Guide Contents
    Symantec™ Endpoint Protection 14.x for Linux Client Guide Contents Chapter 1 Protecting Linux computers with Symantec Endpoint Protection ....................................................... 3 About Symantec Endpoint Protection for Linux ..................................... 3 Symantec Endpoint Protection client for Linux system requirements ........................................................................... 4 Getting started on the Linux client ...................................................... 5 About the Linux client graphical user interface ...................................... 7 What happens when a virus is detected ........................................ 7 Importing client-server communication settings into the Linux client ..................................................................................... 8 Uninstalling the Symantec Endpoint Protection client for Linux ................ 9 Appendix A Symantec Endpoint Protection client for Linux command line reference .............................................. 11 rtvscand ..................................................................................... 12 sav ............................................................................................ 15 savtray ....................................................................................... 22 smcd ......................................................................................... 24 symcfg ....................................................................................... 27 symcfgd ....................................................................................
    [Show full text]
  • KDB+ Quick Guide
    KKDDBB++ -- QQUUIICCKK GGUUIIDDEE http://www.tutorialspoint.com/kdbplus/kdbplus_quick_guide.htm Copyright © tutorialspoint.com KKDDBB++ -- OOVVEERRVVIIEEWW This is a complete quide to kdb+ from kx systems, aimed primarily at those learning independently. kdb+, introduced in 2003, is the new generation of the kdb database which is designed to capture, analyze, compare, and store data. A kdb+ system contains the following two components − KDB+ − the database kdatabaseplus Q − the programming language for working with kdb+ Both kdb+ and q are written in k programming language (same as q but less readable). Background Kdb+/q originated as an obscure academic language but over the years, it has gradually improved its user friendliness. APL 1964, AProgrammingLanguage A+ 1988, modifiedAPLbyArthurWhitney K 1993, crispversionofA + , developedbyA. Whitney Kdb 1998, in − memorycolumn − baseddb Kdb+/q 2003, q language – more readable version of k Why and Where to Use KDB+ Why? − If you need a single solution for real-time data with analytics, then you should consider kdb+. Kdb+ stores database as ordinary native files, so it does not have any special needs regarding hardware and storage architecture. It is worth pointing out that the database is just a set of files, so your administrative work won’t be difficult. Where to use KDB+? − It’s easy to count which investment banks are NOT using kdb+ as most of them are using currently or planning to switch from conventional databases to kdb+. As the volume of data is increasing day by day, we need a system that can handle huge volumes of data. KDB+ fulfills this requirement. KDB+ not only stores an enormous amount of data but also analyzes it in real time.
    [Show full text]
  • Software Conceptual Integrity: Deconstruction, Then Reconstruction
    Software Conceptual Integrity: Deconst, Then Reconst Iaakov Exman Software Conceptual Integrity: Deconstruction, Then Reconstruction Iaakov Exman 1 Software Engineering Department The Jerusalem College of Engineering- Azrieli Jerusalem, Israel [email protected] Computer Classification System Software and its engineering → Software creation and management → Designing software {CCS 2012} Abstract Conceptual Integrity is the most important consideration for software system design, as stated by Frederick Brooks. Brooks also suggested that Conceptual Integrity can be attained by means of design principles, such as Propriety, and Orthogonality. However, Brooks’ principles have not been formalized, posing obstacles to their application in practice, and to a deeper comprehension of Conceptual Integrity. This paper has three goals: first, to achieve deeper comprehension of Conceptual Integrity by deconstructing it into two phases, viz. Conceptualization and Modularization , iteratively applied during software system design; second, to show that the algebraic Linear Software Models already provide the hitherto lacking formalization of Brooks’ design principles, which surprisingly belong mainly to the Modularization phase; third, to reconstruct Conceptualization and Modularization, preserving the desirable tension between: a- phases’ separation , each with its own specific formal manipulation techniques; b- precise transition between these phases, consisting of explicit mutual relationships. The tension stems from the Modularity Matrix linking two
    [Show full text]
  • Krust: a Formal Executable Semantics of Rust
    KRust: A Formal Executable Semantics of Rust Feng Wang∗, Fu Song∗, Min Zhang†, Xiaoran Zhu† and Jun Zhang∗ ∗School of Information Science and Technology, ShanghaiTech University, Shanghai, China †Shanghai Key Laboratory of Trustworthy Computing, East China Normal University, Shanghai, China Abstract—Rust is a new and promising high-level system object is a variable binding. When a variable goes out of its programming language. It provides both memory safety and scope, Rust will free the bound resources. The ownership of thread safety through its novel mechanisms such as ownership, an object can be transferred, after which the object cannot moves and borrows. Ownership system ensures that at any point there is only one owner of any given resource. The ownership of be accessed via the outdated owner. This ensures that there a resource can be moved or borrowed according to the lifetimes. is exactly one binding to any object. Instead of transferring The ownership system establishes a clear lifetime for each value ownership, Rust provides borrows which allows an object to and hence does not necessarily need garbage collection. These be shared by multiple references. There are two kinds of novel features bring Rust high performance, fine low-level control borrows in Rust: mutable references and immutable references. of C and C++, and unnecessity in garbage collection, which differ Rust from other existing prevalent languages. For formal A mutable reference can mutate the borrowed object if the analysis of Rust programs and helping programmers learn its object is mutable, while an immutable reference cannot mutate new mechanisms and features, a formal semantics of Rust is the borrowed object even the object itself is mutable.
    [Show full text]
  • A Declarative Metaprogramming Language for Digital Signal
    Vesa Norilo Kronos: A Declarative Centre for Music and Technology University of Arts Helsinki, Sibelius Academy Metaprogramming PO Box 30 FI-00097 Uniarts, Finland Language for Digital [email protected] Signal Processing Abstract: Kronos is a signal-processing programming language based on the principles of semifunctional reactive systems. It is aimed at efficient signal processing at the elementary level, and built to scale towards higher-level tasks by utilizing the powerful programming paradigms of “metaprogramming” and reactive multirate systems. The Kronos language features expressive source code as well as a streamlined, efficient runtime. The programming model presented is adaptable for both sample-stream and event processing, offering a cleanly functional programming paradigm for a wide range of musical signal-processing problems, exemplified herein by a selection and discussion of code examples. Signal processing is fundamental to most areas handful of simple concepts. This language is a good of creative music technology. It is deployed on fit for hardware—ranging from CPUs to GPUs and both commodity computers and specialized sound- even custom-made DSP chips—but unpleasant for processing hardware to accomplish transformation humans to work in. Human programmers are instead and synthesis of musical signals. Programming these presented with a very high-level metalanguage, processors has proven resistant to the advances in which is compiled into the lower-level data flow. general computer science. Most signal processors This programming method is called Kronos. are programmed in low-level languages, such as C, often thinly wrapped in rudimentary C++. Such a workflow involves a great deal of tedious detail, as Musical Programming Paradigms these languages do not feature language constructs and Environments that would enable a sufficiently efficient imple- mentation of abstractions that would adequately The most prominent programming paradigm for generalize signal processing.
    [Show full text]