DOCSLIB.ORG

For C Programmers

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
For C Programmers J For C Programmers Henry Rich 2006/04/15 (J6.01) Copyright © 2004, 2006 Henry H. Rich. All rights reserved. Send comments to [email protected] Foreword You are an experienced C programmer who has heard about J, and you think you'd like to see what it's all about. Congratulations! You have made a decision that will change your programming life, if only you see it through. The purpose of this book is to help you do that. It won't be easy, and it certainly won't be what you're expecting. You've learned languages before, and you know the drill: find out how variables are declared, learn the syntax for conditionals and loops, learn how to call a function, get a couple of examples to edit, and you're a coder. Fuggeddaboutit! In J, there are no declarations, seldom will you see a loop, and conditionals often go incognito. As for coding from examples, well, most of our examples are only a couple of lines of code—you won't get much momentum from that! You're just going to have to grit your teeth and learn a completely new way to write programs. Why should you bother? To begin with, for the productivity. J programs are usually a fifth to a tenth as long as corresponding C programs, and along with that economy of expression comes coding speed. Next, for the programming environment: J is an interpreted language, so your programs will never crash, you can modify code while it's running, you don't have to deal with makefiles and linking, and you can test your code simply by entering it at the keyboard and seeing what it does. If you stick with it, J won't just help the way you code, it'll help the way you think. C is a computer language; it lets you control the things the computer does. J is a language of computation: it lets you describe what needs to be done without getting bogged down in details (but in those details, the efficiency of its algorithms is extraordinary). Because J expressions deal with large blocks of data, you will stop thinking of individual numbers and start thinking at a larger scale. Confronted with a problem, you will immediately break it down into pieces of the proper size and express the solution in J—and if you can express the problem, you have a J program, and your problem is solved. Unfortunately, it seems to be the case that the more experience you have as a C programmer, the less likely you are to switch to J. This may not be because prolonged exposure to C code limits your vision and contracts the scope of your thinking to the size of a 32-bit word—though studies to check that are still under way and it might be wise for you to stop before it's too late—but because the better you are at C, the more you have to lose by switching to J. You have developed a number of coding habits: for example, how to manage loops to avoid errors at extreme cases; how to manage pointers effectively; how to use type-checking to avoid errors. None of that will be applicable to J. J will take advantage of your skill in grasping the essence of a problem—indeed, it will develop that skill considerably by making it easier for you to express what you grasp—but you will go through a period during which it will seem like it takes forever to get things done. During that period, please remember that to justify your choice of J, you don't have to be as expert in J as you were in C; you only have to be more productive in J than you ii were in C. That might well happen within a month. After you have fully learned J, it will usually be your first choice for describing a program. Becoming a J programmer doesn't mean you'll have to give up C completely; every language has its place. In the cases where you want to write code in C (either to use a library you have in C or to write a DLL for a function that is inefficiently computed in J), you will find interfacing J to DLLs to be simple and effective. This book's goal is to explain rudimentary J using language familiar to a C programmer. After you finish reading it, you should do yourself the honor of carefully reading the J Dictionary, in which you can learn the full language, one of the great creations in computer science and mathematics. Acknowledgements I am obliged to the reviewers who commented on earlier versions: Michel Dumontier, Ken Iverson, Fraser Jackson, David Ness, Richard Payne, Ewart Shaw, and Keith Smillie. Brian Schott, Nicholas Spies, and Norman Thomson exchanged emails with me at length to smooth over rough spots. David Steele conducted a painstaking review of several early drafts and suggested many changes great and small. Björn Helgason translated the text into Icelandic, finding a number of errors along the way. Kip Murray's 'review' became more of a dismantling, cleaning, and reassembly operation in which large sections of prose were rewritten as he pointed out to me their essential meaninglessness; the reader should be as grateful to him as I am. Without the patient explanations of my early teachers in J, Raul Miller and Martin Neitzel, I would have given up on J. I hope that this book pays to others the debt I owe to them. My current happy career as a J programmer would not have been possible without the work of the staff at Jsoftware, Inc., who created J. For the patriarch, the late Ken Iverson, I am unworthy to express admiration: I have only awe. I hope his achievement eases the lives of programmers for generations to come. To the rest, both Iversons and non- Iversons, I give my thanks. The implementation of the J interpreter has required diverse skills: architectural vision, careful selection of algorithms, cold-eyed project management to select features for implementation, robust and efficient coding, performance optimization, and expertise in numerical analysis. Most improbably, all these talents have resided in one man, Roger Hui il miglior fabbro. J gives us all a way to have a little of Roger's code in our own. We should aspire no higher. Change History 2002/6/18: Add chapters on mathematics in J, and section on Symbols; minor changes to wording; bring text up to J Release 5.01 2002/8/16: Minor additions; added section on aliasing; added chapter on sockets 2002/9/26: Added sections on fndisplay, integrated rank support, and ordering of implied loops iii 2002/11/14 Added explanatory sections, section on the J Performance Monitor, and chapter on Error Messages 2003/07/18 (J5.03) added section on I., updated f. Added chapter on frequent errors. Added section on run-length decoding 2004/10/31 (J5.04) ^:a:, vector cut. Added chapter on Sequential Machines 2004/11/22 Added section on monad { 2005/04/14 Fixed discussion of throw. 2005/09/03 (J6.01) added chapter on Graphics, discussion of noun forks, section on Fast Searching, section on CRC. Switched chapters 10 & 11, and added pictorial discussion of @ and @: . Added example on partitions. Added section on 3!:4 5 conversions. Explained the difference between (number number) and (noun noun). 2006/01/25 Account for 6.01 changes. Describe dyad I. Discuss 8!:n 2006/03/10 (J6.01 final): New parameters x, y, etc. Discuss dyad p: Update dyad ;: . Add discussion of precision. Describe assignment in tacit definition. Move chapter on Performance, and add recommendations for high-performance code. Improve discussion of object programming. 2006/04/15 Fix section on ;.0 . Elucidate L: . iv Contents Foreword............................................................................................................................. ii Acknowledgements..................................................................................................iii Change History ........................................................................................................iii 1. Introduction................................................................................................................. 12 2. Culture Shock.............................................................................................................. 13 Programming In J 16 3. Preliminaries ............................................................................................................... 17 Notation Used in This Book ................................................................................... 17 Terminology............................................................................................................ 17 Sentences (statements) ......................................................................................... 18 Word Formation (tokenizing rules) ...................................................................... 18 Numbers.................................................................................................................. 19 Adjacent Numbers Form a Single Word ............................................................ 19 Adjacent Named Nouns Do NOT Form a Single Word..................................... 20 Characters ............................................................................................................... 20 Valence of Verbs (Binary and Unary Operators)............................................... 20 How Names (Identifiers) Get Assigned................................................................. 21 Order of Evaluation ................................................................................................ 21 How Names Are Substituted................................................................................... 22 What a verb (function) looks like........................................................................... 23 Running a J program..............................................................................................
Load more

Recommended publications
  • NOVEMBER 18 • WEDNESDAY Build Stuff'15 Lithuania
    Build Stuff'15 Lithuania NOVEMBER 18 • WEDNESDAY A Advanced B Beginner I Intermediate N Non­Technical 08:30 – 09:00 Registration 1. Alfa Speakers: Registration 09:00 – 09:15 Welcome talk 1. Alfa Speakers: Welcome talk 09:00 – 18:00 Open Space 6. Lobby Speakers: Open Space Sponsors: 4Finance, Devbridge, Storebrand, Visma Lietuva, WIX Lietuva 09:15 – 10:15 B Uncle Bob / Robert Martin @unclebobmartin ­ The Last Programming Language 1. Alfa Speakers: Uncle Bob / Robert Martin For the last 50 years we’ve been exploring language after language. Now many of the “new” languages are actually quite old. The latest fad is “functional programming” which got it’s roots back in the 50s. Have we come full circle? Have we explored all the different kinds of languages? Is it time for us to finally decide on a single language for all software development? In this talk Uncle Bob walks through some of the history of programming languages, and then prognosticates on the future of languages. 10:15 – 10:35 Coffee/tea break 1. Alfa Speakers: Coffee/tea break 10:35 – 11:30 I Dmytro Mindra @dmytromindra ­ Refactoring Legacy Code 5. Theta Speakers: Dmytro Mindra Every programmer has to face legacy code day after day. It might be ugly, it might look scary, it can make a grown man cry. Some will throw it away and try rewriting everything from scratch. Most of them will fail. Refactoring legacy code is a much better idea. It is not so scary when you take it in very small bites, introduce small changes, add unit tests.
    [Show full text]
  • The Best of Both Worlds?
    The Best of Both Worlds? Reimplementing an Object-Oriented System with Functional Programming on the .NET Platform and Comparing the Two Paradigms Erik Bugge Thesis submitted for the degree of Master in Informatics: Programming and Networks 60 credits Department of Informatics Faculty of mathematics and natural sciences UNIVERSITY OF OSLO Autumn 2019 The Best of Both Worlds? Reimplementing an Object-Oriented System with Functional Programming on the .NET Platform and Comparing the Two Paradigms Erik Bugge © 2019 Erik Bugge The Best of Both Worlds? http://www.duo.uio.no/ Printed: Reprosentralen, University of Oslo Abstract Programming paradigms are categories that classify languages based on their features. Each paradigm category contains rules about how the program is built. Comparing programming paradigms and languages is important, because it lets developers make more informed decisions when it comes to choosing the right technology for a system. Making meaningful comparisons between paradigms and languages is challenging, because the subjects of comparison are often so dissimilar that the process is not always straightforward, or does not always yield particularly valuable results. Therefore, multiple avenues of comparison must be explored in order to get meaningful information about the pros and cons of these technologies. This thesis looks at the difference between the object-oriented and functional programming paradigms on a higher level, before delving in detail into a development process that consisted of reimplementing parts of an object- oriented system into functional code. Using results from major comparative studies, exploring high-level differences between the two paradigms’ tools for modular programming and general program decompositions, and looking at the development process described in detail in this thesis in light of the aforementioned findings, a comparison on multiple levels was done.
    [Show full text]
  • On the Cognitive Prerequisites of Learning Computer Programming
    On the Cognitive Prerequisites of Learning Computer Programming Roy D. Pea D. Midian Kurland Technical Report No. 18 ON THE COGNITIVE PREREQUISITES OF LEARNING COMPUTER PROGRAMMING* Roy D. Pea and D. Midian Kurland Introduction Training in computer literacy of some form, much of which will consist of training in computer programming, is likely to involve $3 billion of the $14 billion to be spent on personal computers by 1986 (Harmon, 1983). Who will do the training? "hardware and software manu- facturers, management consultants, -retailers, independent computer instruction centers, corporations' in-house training programs, public and private schools and universities, and a variety of consultants1' (ibid.,- p. 27). To date, very little is known about what one needs to know in order to learn to program, and the ways in which edu- cators might provide optimal learning conditions. The ultimate suc- cess of these vast training programs in programming--especially toward the goal of providing a basic computer programming compe- tency for all individuals--will depend to a great degree on an ade- quate understanding of the developmental psychology of programming skills, a field currently in its infancy. In the absence of such a theory, training will continue, guided--or to express it more aptly, misguided--by the tacit Volk theories1' of programming development that until now have served as the underpinnings of programming instruction. Our paper begins to explore the complex agenda of issues, promise, and problems that building a developmental science of programming entails. Microcomputer Use in Schools The National Center for Education Statistics has recently released figures revealing that the use of micros in schools tripled from Fall 1980 to Spring 1983.
    [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]
  • 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]
  • Keir, Paul G (2012) Design and Implementation of an Array Language for Computational Science on a Heterogeneous Multicore Architecture
    Keir, Paul G (2012) Design and implementation of an array language for computational science on a heterogeneous multicore architecture. PhD thesis. http://theses.gla.ac.uk/3645/ Copyright and moral rights for this thesis are retained by the author A copy can be downloaded for personal non-commercial research or study, without prior permission or charge This thesis cannot be reproduced or quoted extensively from without first obtaining permission in writing from the Author The content must not be changed in any way or sold commercially in any format or medium without the formal permission of the Author When referring to this work, full bibliographic details including the author, title, awarding institution and date of the thesis must be given Glasgow Theses Service http://theses.gla.ac.uk/ [email protected] Design and Implementation of an Array Language for Computational Science on a Heterogeneous Multicore Architecture Paul Keir Submitted in fulfilment of the requirements for the degree of Doctor of Philosophy School of Computing Science College of Science and Engineering University of Glasgow July 8, 2012 c Paul Keir, 2012 Abstract The packing of multiple processor cores onto a single chip has become a mainstream solution to fundamental physical issues relating to the microscopic scales employed in the manufac- ture of semiconductor components. Multicore architectures provide lower clock speeds per core, while aggregate floating-point capability continues to increase. Heterogeneous multicore chips, such as the Cell Broadband Engine (CBE) and modern graphics chips, also address the related issue of an increasing mismatch between high pro- cessor speeds, and huge latency to main memory.
    [Show full text]
  • Boost.Higherorderfunctions Documentation Release 0.6
    Boost.HigherOrderFunctions Documentation Release 0.6 Paul Fultz II Sep 16, 2021 Contents 1 Introduction 3 1.1 About...................................................3 1.2 Motivation................................................4 1.3 Requirements...............................................4 1.3.1 Contexpr support........................................4 1.3.2 Noexcept support........................................4 1.4 Building.................................................4 1.4.1 Installing............................................4 1.4.2 Tests...............................................4 1.4.3 Documentation.........................................5 1.5 Getting started..............................................5 1.5.1 Higher-order functions.....................................5 1.5.2 Function Objects........................................6 1.5.3 Lifting functions........................................6 1.5.4 Declaring functions.......................................7 1.5.5 Adaptors............................................7 1.5.6 Lambdas............................................8 1.6 Examples.................................................8 1.6.1 Print function..........................................8 1.6.2 Conditional overloading.................................... 12 1.6.3 Polymorphic constructors.................................... 14 1.6.4 More examples......................................... 15 1.7 Point-free style programming...................................... 16 1.7.1 Variadic print.........................................
    [Show full text]
  • Casualty Actuarial Society E-Forum, Summer 2018
    Casualty Actuarial Society E-Forum, Summer 2018 The CAS E-Forum, Summer 2018 The Summer 2018 edition of the CAS E-Forum is a cooperative effort between the CAS E-Forum Committee and various CAS committees, task forces, working parties and special interest sections. This E-Forum contains a report of the CAS Working Party on Sustainable ERM (SERM) and two independent research papers. The CAS Working Party on Sustainable ERM (SERM) Fan Yang, Chairperson Sandra J. Callanan, FCAS Voon Seng Lai, FCAS George E. Davis, FCAS Tom Wakefield Casualty Actuarial Society E-Forum, Summer 2018 i CAS E-Forum, Summer 2018 Table of Contents Working Party Report Introduction to Sustainable ERM CAS Working Party on Sustainable ERM (SERM) ................................................................................ 1-26 Independent Research Property-Casualty Liability Estimation Reimagined Christopher Gross, ACAS, MAAA ........................................................................................................... 1-14 Actuarial Models in the Language J (Including 2 scripts: act.ijs and rubik.ijs) Richard L. Vaughan, FCAS, FSA, MAAA ............................................................................................... 1-69 Casualty Actuarial Society E-Forum, Summer 2018 ii E-Forum Committee Derek A. Jones, Chairperson Mark M. Goldburd Karl Goring Timothy C. Mosler Bryant Russell Shayan Sen Rial Simons Brandon S. Smith Elizabeth A. Smith, Staff Liaison/Staff Editor John Sopkowicz Zongli Sun Betty-Jo Walke Janet Qing Wessner Windrie Wong
    [Show full text]
  • Functional Programming: What Why and How
    4/12/2018 Functional Programming: What Why and How Functional Programming What, Why and How Just twitted the slides @JSDude005 ThatJSDude.com youtube.com/ThatJSDude file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 1/114 4/12/2018 Functional Programming: What Why and How file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 2/114 4/12/2018 Functional Programming: What Why and How We will talk about Three Basics of Functional Programming Five Popular patterns and techniques Three higher level Geeky things Compare OOP with FP Transform OOP to FP ...and lots of fun file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 3/114 4/12/2018 Functional Programming: What Why and How WhyWhy file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 4/114 4/12/2018 Functional Programming: What Why and How FP ShinesFP Shines Cloud/Big Data for data processing, filtering, aggregating Easier to figure out what the hell is going on in a larger code base Concepts are used in web application Easier to read, maintain, test Avoid a mess of states or multi threading issues Ref: Why FP matters file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 5/114 4/12/2018 Functional Programming: What Why and How WhatWhat file:///Users/jhankarmahbub/Documents/git/functional-programming/index.html#/24 6/114 4/12/2018 Functional Programming: What Why and How Ask the geeky guy Monads, Monoids, Lift, Functors, actuators Immutable, Higher Order, Tail call
    [Show full text]
  • Design Strategies and Knowledge in Object-Oriented Programming: Effects of Experience
    Published in Human-Computer Interaction, 1995, 10 (2 & 3), 129-170. http://hci-journal.com/ Design Strategies and Knowledge in Object-Oriented Programming: Effects of Experience Françoise Détienne* Projet de Psychologie Ergonomique INRIA Domaine de Voluceau, Rocquencourt, BP 105, 78153 Le Chesnay, cedex, France. running head title: Design Strategies and knowledge in OOP * Françoise Détienne is a cognitive psychologist with an interest in software design; she is a researcher in the Ergonomic Psychology group of INRIA. Published in Human-Computer Interaction, 1995, 10 (2 & 3), 129-170. http://hci-journal.com/ ABSTRACT An empirical study was conducted to analyse design strategies and knowledge used in object-oriented software design. Eight professional programmers experienced with procedural programming languages and either experienced or not experienced in object- oriented programming participated in this experiment. They were asked to design a program for a procedural problem and a declarative problem. We have concentrated our analysis on the design strategies related to two central aspects of the object-oriented paradigm: (1) associating actions, i.e., execution steps, of a complex plan to different objects and revising a complex plan, and (2) defining simple plans at different levels in the class hierarchy. As regards the development of complex plans elements attached to different objects, our results show that, for beginners in OOP, the description of objects and the description of actions are not always integrated in an early design phase, particularly for the declarative problem whereas, for the programmers experienced in OOP, the description of objects and the description of actions tend to be integrated in their first drafts of solutions whichever the problem type.
    [Show full text]
  • A Rule Based Approach to Program Development
    AN ABSTRACT OF THE THESIS OF Abbas Birjandi for the degree of Doctor of Philosophy in Computer Science presented on May 30, 1986. Title: A Rule Based Approach To Program Development 1^, Redacted for Privacy Abstract approved: V-.... .....r Theodore G. Lewis A rule based transformational model for program development anda meta- tool based on the above model is presented. The meta-toolcan be instantiated to create various program development tools such as tools for building reusable software components, language directed editors, language to language translators, program instrumentation, structured document generator, and adaptive language based prettyprinters. This new rule based approach has two important features:1) it is language independent and can be applied to various languages, and 2) provides a powerful escape mechanism for extending the semantics of the rules. Instances of the meta-tool for restructuring source programs for building ab- stract components and their refinement to concrete instances, source-to-source trans- lation, and source contraction and expansion tools for improving readability and understanding are described. A Rule Based Approach To Program Development By Abbas Birjandi A Thesis submited to Oregon State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy Completed May 30, 1986 Commencement June 1987 APPROVED: , _ Redacted for Privacy Professor of Computer Science in charge of major Redacted for Privacy Head of Department of Computer Science Redacted for Privacy Dean of G a to School ci Date thesis presented May 30, 1986 DEDICATION This dissertation is dedicated to Dr. Bruce D. Shriver for whom I will always be a student and friend.
    [Show full text]
  • Functional Modelling of Operating Systems
    BABES¸-BOLYAI UNIVERSITY, CLUJ-NAPOCA FACULTY OF MATHEMATICS AND COMPUTER SCIENCE EOTV¨ OS¨ LORANT´ UNIVERSITY, BUDAPEST FACULTY OF INFORMATICS Functional Modelling of Operating Systems Abstract of Doctoral Thesis PALI´ G´abor J´anos Horia F. POP (BBU) Doctoral Student KOZSIK Tam´as(ELTE) Supervisors Cluj-Napoca, March 2012 Contents Contents of the Thesis 1 Keywords 3 Introduction 3 1 Fundamental Problems 5 2 Employed Techniques 6 3 Composing Little Languages into Applications 8 4 Real World Execution of Flows 11 5 Flow Programs as Operating Systems 15 6 Related Work 19 7 Conclusion and Future Work 22 References 25 Contents of the Thesis Introduction 1 Fundamental Problems 1.1 Synopsis 1.2 Abstraction Versus Performance 1.3 Advantages of Higher Level Approaches 1.4 Related Work 1.4.1 Abstractions in Operating Systems 2 Employed Techniques 2.1 Synopsis 2.2 Language Embedding 2.3 Building a Language Core 2.4 Generic Optimizations in the Frontend 2.5 Target-Specific Optimizations in the Backend 2.6 Summary 3 Composing Little Languages into Applications 3.1 Synopsis 3.2 The Flow Language 3.3 Global Configuration and Events 3.4 The Flow Types 3.5 The Flow Kernels 3.6 The Flow Constructors 1 3.6.1 Examples 3.7 Abstract Programs 3.7.1 Graph Decomposition 3.7.2 Channels 3.7.3 Tasks 3.7.4 Mapping Flows to Programs 3.8 Semantics 3.8.1 State Transformers 3.9 Summary 4 Real World Execution of Flows 4.1 Synopsis 4.2 Executing Tasks 4.3 The Pool of Tasks 4.4 Memory Management 4.5 Scheduling 4.5.1 Marking Boundaries for Kernels 4.5.2 Selectors 4.5.3 Creating
    [Show full text]