DOCSLIB.ORG

A Taxonomic Analysis of Typographic Programming Style

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

AN ABSTRACT OF THE THESIS OF Paul W. Oman. Jr, for the degree of Doctor of Philosophy in ComputerScience presented on December 12. 1988. Title: A Taxonomic Analysis of Typographic Programming Style Redacted for Privacy Abstract approved: Curtis R. Cook Program comprehension is important in program testing, debugging, andmaintenance. Programming style impacts program understanding. However, there has not been any systematic identification of individual style factors and their contribution to program comprehension. In this thesis we present a programming style taxonomy composed of threeclasses: typographic (program layout and commenting), control structures, and information structures. Each class is further subdivided into macro (whole program orsystem) and micro (module or statement) subclasses. The taxonomy reveals many conflicting and unsubstantiated rules in collections of style rules from various publications on programming style. Further, it provides plausible explanations for some of the inconsistent results in programming style research. This thesis concentrates on the isolation of typographic style factors andanalysis of their affects on programmer comprehension. General principles of good macro- andmicro- typographic style are identified and the "book paradigm," a mechanism for implementing the principles, is presented. Four experiments, involving both student andprofessional programmers, demonstrate that the macro- andmicro-typographic principles incorporated into the book paradigm significantly improved program comprehensionand maintenance. These results have direct application to programming language designand programming tools such as pretty-printers, language directed editors, style analyzers,and source code control systems. A Taxonomic Analysis of Typographic ProgrammingStyle by Paul W. Oman, Jr. A THESIS submitted to Oregon State University in partial fulfillment of the requirements for the degree of Doctor of Philosophy Completed December 1988 Commencement June 1989 APPROVED: Redacted for Privacy Professor ofComputer Science in Charge ofMajor Redact 6d for Privacy Headof Department of Computer Science Redacted for Privacy Dean of GraduVchool Q Date thesis is presented December 12. 1988 Typed by Paul Oman ACKNOWLEDGEMENTS I would like to express my appreciation to each member of my committee for their time and patience. To Curt Cook, my major advisor, thanks for sticking with me when I got off track. Your insistence on excellence is responsible for the quality and thoroughness of this thesis. To Ted Lewis, Editor-in-Chief ofSoftware,your criticism of my proposal is responsible for the (re)organization of this thesis. Also, thank you for giving me the opportunity to get involved withSoftware.To Toshi Minoura, your probing questions are responsible for most of Chapter 3, which is the glue that holds this thesis together, thank you. To Walter Loveland, my graduate representative, thank you for your positive support and assistance. And last, to Donna Cruse, who has guided me without knowing it since 1970, thank you for giving me a strong foundation in science. Your influence can be seen throughout this thesis. I would also like to express my appreciation to the people who have aided and supported this research. From the University of Idaho I have received much support from William Saul, Dean of the College of Engineering, Richard Jacobsen, Associate Dean, and John Dickinson, Chair of the Computer Science Department. At O.S.U., thanks are due to Lyle Calvin, Dean of the Graduate School, and Walter Rudd, Chair of the Computer Science Department. Thank you all. Finally, I would also like to express my thanks to my family for their patience and support. You have made it a joy to "come home." My success is founded in your love and encouragement. Thank you. Table of Contents page 1. Introduction 1 1.1. What is "programming style" ? 1 1.2. The problems in programming style research. 2 1.3.Rationale for a taxonomic analysis of style. 3 1.4.Scope of this thesis. 4 1.5.Organization of this thesis. 5 2. An Overview of Programming Style Research 7 2.1.Studies on programming style. 7 2.2.Style guidelines. 7 2.3. Automated style analyzers. 9 2.4. Code formatters. 11 2.5. Programmer comprehension studies. 12 2.6.Conclusions. 14 3. A Programming Style Taxonomy 15 3.1.Building a style taxonomy. 15 3.2.Verifying the taxonomy. 19 3.3. A taxonomic look at programming style rules. 19 3.3.1. Widely held but unsubstantiated rules. 20 3.3.2. Incompatible style rules. 23 3.3.3. Tacit misconceptions on programming style. 25 3.4.Conclusions. 25 4. Analyzing Typographic Style 27 4.1. The benefits of taxonomic analysis. 27 4.2.Indices of style. 27 4.2.1. An early attempt to "capture" style. 28 4.2.2. Typographic style analysis. 29 4.3. The affects of style on programmer comprehension. 34 4.3.1. First nested IF experiment. 34 4.3.2. Second nested IF experiment. 38 4.4. Conclusions. 41 5. Towards Better TypographicStyle 42 5.1. The problems with today'stypographic style. 42 5.2. An overview of programmercomprehension theory. 42 5.3. An overview of program maintenanceactivity. 44 5.4. A generic comprehension andmaintenance model. 45 46 5.5.Principles of typographic style. 6. The Book Paradigm forTypographic Style 49 49 6.1.Introduction. 6.2. The book paradigm. 49 6.3. Macro-typographic book paradigmformatting. 51 6.4. Micro-typographic book paradigmformatting. 52 6.5. An example "book" program listing. 53 6.6.Conclusions. 58 7. Testing the Book ProgramListing 59 7.1. Introduction. 59 7.2. Testing macro-typographic principles. 59 7.2.1. Experiment 1: A macro-typographiccomparison. 59 7.2.2. Conclusions from Experiment 1. 64 7.3.Testing micro-typographic principles. 64 7.3.1. Experiment 2: Micro-typographic Pascalformatting. 64 7.3.2. Experiment 3: Micro-typographic Cformatting. 68 7.3.3. Conclusions from Experiments 2 &3. 72 7.4. Testing the complete book formatlisting. 72 7.4.1. Experiment 4: Empirical studieswith "real" programmers. 73 7.4.2. Studying with "Think aloud" protocols. 75 7.4.3. The oral comprehension test. 78 7.4.4. Creating a call graph. 81 7.4.5. Responses to open-ended questions. 84 7.4.6. Conclusions from Experiment 4. 85 7.5. Conclusions from Experiments 1 through 4. 85 8. Conclusions 86 8.1. Review of results. 86 8.2. Future work. 87 Bibliography 90 Appendices A. Composite Listing of Style Rules 98 B. Nested IF Experiments Sample Test Packet 105 C. Experiment 1: Macro-typographic Experiment Instructions 107 D. Experiment 2: Pascal Micro-typographic Experiment Sample Test Packet 108 E. Experiment 3: C Micro-typographic Experiment Sample Test Packet 112 F. Experiment 4: Empirical Studies Experiment Sample Test Packet 116 List of Figures Figures Page 3.1. A Style Taxonomy 16 3.2. Style Taxonomy Definition 17 3.3. Widely Held Style Guidelines 22 3.4. Incompatible Style Rules 24 3.5. Tacit Misconceptions About Programming Style 26 4.1. Cluster Analysis of Textbook Authors 32 4.2. Cluster Analysis of Industrial Code 33 4.3. IF Statements for First Nested IF Experiment 35 4.4. Scores and Times from First Nested IF Experiment 37 4.5. IF Statements for Second Nested IF Experiment 38 4.6. Scores and Times from Second Nested IF Experiment 40 6.1. An Example Book Format Listing 54 7.1. Experiment 1: Skip_Blanks Procedure 60 7.2. Experiment 1: Editor Table of Contents 61 7.3. Experiment 2: Pascal Code Excerpts 65 7.4. Scores and Times from Experiment 2 67 7.5. Experiment 3: C Code Excerpts 69 7.6. Scores and Times from Experiment 3 71 7.7. Scores and Times from Experiment 4 Comprehension Test 80 7.8. Scores and Times from Experiment 4 Call Graph Exercise 83 List of Tables Table Page 4.1. Typographic Style Vectors for TextbookData 31 4.2. Results from First Nested IF Experiment 37 4.3. Results from Second Nested IFExperiment 40 7.1. Experiment 1: Ability to WriteSkip_Blanks 62 7.2. Experiment 1: Identifying Skip_BlanksCalls 63 7.3. Experiment 2: Results from PascalCode Comparison 67 7.4. Experiment 3: Results from C CodeComparison 71 7.5. Experiment 4: Professional Programmers'Experience 75 7.6. Experiment 4: Results fromComprehension Test 80 7.7. Experiment 4: Results from CallGraph Exercise 83 A Taxonomic Analysis of TypographicProgramming Style Chapter 1 Introduction 1.1. What is "programming style"? Programming style is an intuitive and elusive concept.It is highly individualistic and easily recognized, yet difficult to define or quantify.The goal of programming style is to make a program clear, easy to understand andthereby easy to work with. The following illustrate the diversity in attempts to defineprogramming style. "The 'elegance' or 'style' of a program is sometimesconsidered a nebulous attribute that is somehow unquantifiable; a programmerhas an instinctive feel for a 'good' or 'bad' program ..." [Berr85,p.80] Programming style ... "refers to the entire set ofconventions, guidelines, aids and rules that make computer programs easier forpeople to read, work with and understand." -- [Schn81,p.52] "Programming style brings to mind the ways that acreative programmer brings clarity, maintainability, testability, reliability,and efficiency to the coding of a module." -- [Arth85,p.173] These definitions reflect different views ofprogramming style and, although diverse, they are not at odds with dictionary definitionsof style: "1. a way of speaking or writing, one characteristicof an individual, period, school, or nation; 2. the custom or plan followedin spelling, capitalization, punctuation, and typographic arrangement and display;3. the manner or method of acting or performing as sanctioned by somestandard; 4. a distinctive or characteristic manner." -- [Merr74] Programming style shares many similarities withliterary writing style. For example, in his book on technical writing Chael Markellists word choice, sentence construction, and paragraph structure as elements ofliterary style [Mark84,p.89]. However, effective writing is more than observing establishedconventions for spelling, grammar, or sentence structure.
Recommended publications
  • American Sociological Association Style Guide

    American Sociological Association Style Guide

    AMERICAN Copyright @ 1997 by the American Sociological Association SOCIOLOGICAL All rights reserved. No part of this book may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopy­ ASSOCIATION ing, recording, or by any information storage or retrieval system, without permission in writing frm the publisher. Cite as: American Sociological Association. 1997. American SociologicalAssociation Style Guide.2nd ed. Washington, DC: American Sociological Association. For information: American Sociological Association 1307 New York Avenue NW Washington, DC 20005-4701 (202) 383-9005 e-mail: [email protected] ISBN 0-912764-29-5 SECOND EDITION About the ASA The American Sociological Association (ASA), founded in 1905, is a non-profit membership association dedicated to serving sociologists in their work, advancing sociology as a scientific discipline and profession, and promoting the contributions and use of sociology to society. As the national organization for over 13,000 sociologists, the American Sociological Association is well positioned to provide a unique set of benefits to its members and to promote the vitality, visibility, and diversity of the discipline. Working at the national and international levels, the Association aims to articulate policy and implement programs likely to have the broadest possible impact for sociology now and in the future. Publications ASA publications are key to the Association's commitment to scholarly exchange and wide dissemination of sociological knowledge. ASA publications include eight journals (described below); substantive, academic, teaching, and career publications; and directories including the Directoryof Members,an annual Guideto GraduateDepartments of Sociology,a biannual Directory of Departmentsof Sociology,and a Directoryof Sociologistsin Policyand Practice.
  • Indesign CC 2015 and Earlier

    Indesign CC 2015 and Earlier

    Adobe InDesign Help Legal notices Legal notices For legal notices, see http://help.adobe.com/en_US/legalnotices/index.html. Last updated 11/4/2019 iii Contents Chapter 1: Introduction to InDesign What's new in InDesign . .1 InDesign manual (PDF) . .7 InDesign system requirements . .7 What's New in InDesign . 10 Chapter 2: Workspace and workflow GPU Performance . 18 Properties panel . 20 Import PDF comments . 24 Sync Settings using Adobe Creative Cloud . 27 Default keyboard shortcuts . 31 Set preferences . 45 Create new documents | InDesign CC 2015 and earlier . 47 Touch workspace . 50 Convert QuarkXPress and PageMaker documents . 53 Work with files and templates . 57 Understand a basic managed-file workflow . 63 Toolbox . 69 Share content . 75 Customize menus and keyboard shortcuts . 81 Recovery and undo . 84 PageMaker menu commands . 85 Assignment packages . 91 Adjust your workflow . 94 Work with managed files . 97 View the workspace . 102 Save documents . 106 Chapter 3: Layout and design Create a table of contents . 112 Layout adjustment . 118 Create book files . 121 Add basic page numbering . 127 Generate QR codes . 128 Create text and text frames . 131 About pages and spreads . 137 Create new documents (Chinese, Japanese, and Korean only) . 140 Create an index . 144 Create documents . 156 Text variables . 159 Create type on a path . ..
  • From SAS ASCII Output to Word Document

    From SAS ASCII Output to Word Document

    From SASÒ ASCII Output to Word Document – A SASÒ Macro Approach Jianlin ‘Jay’ Zhou, Quintiles, Inc., Kansas City, MO table with multiple pages. Yam (2000) described a method used to ABSTRACT generate Word tables by transferring SAS data to Excel with Dynamic Data Exchange (DDE), which serves as an intermediary for Generating SAS ASCII output directly with PROC REPORT or a repackaging SAS data with a Visual Basic for Application (VBA) DATA _NULL_ step is the most common method used by SAS macro and interfacing with Word via Object Linking and Embedding programmers in the pharmaceutical industry. However, because of (OLE) to get the Excel table into Word. With this method, 24 SAS the many limitations of SAS ASCII files for presentation and variables must be derived in order to instruct Excel to format a table handling, more and more medical writers, biostatisticians, appropriately. Therefore, the process may be time-consuming and publishers, and expert reviewers now request SAS reports in Word difficult to maintain. Within Quintiles, some of my colleagues insert document format. This paper introduces a macro that provides a a text file or copy the SAS output from the SAS output window and process to produce aesthetically improved Word documents with paste it into Word, then run a VBA macro to format the output and very limited programming effort. The macro was designed to expand save it as Word document. The method is very simple and easy, but the presentation capability of ASCII files, to accommodate various only one file is processed at a time and some minor manual effort is fonts, font sizes, and margins, to add one of eighteen pagination required.
  • Magazine Layout and Pagination

    Magazine Layout and Pagination

    XML Professional Publisher: Magazine Layout and Pagination for use with XPP 9.0 September 2014 Notice © SDL Group 1999, 2003-2005, 2009, 2012-2014. All rights reserved. Printed in U.S.A. SDL Group has prepared this document for use by its personnel, licensees, and customers. The information contained herein is the property of SDL and shall not, in whole or in part, be reproduced, translated, or converted to any electronic or machine-readable form without prior written approval from SDL. Printed copies are also covered by this notice and subject to any applicable confidentiality agreements. The information contained in this document does not constitute a warranty of performance. Further, SDL reserves the right to revise this document and to make changes from time to time in the content thereof. SDL assumes no liability for losses incurred as a result of out-of-date or incorrect information contained in this document. Trademark Notice See the Trademark Notice PDF file on your SDL product documentation CD-ROM for trademark information. U.S. Government Restricted Rights Legend Use, duplication or disclosure by the government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 or other similar regulations of other governmental agencies, which designate software and documentation as proprietary. Contractor or manufacturer is SDL Group, 201 Edgewater Drive, Wakefield, MA 01880-6216. ii Contents About This Manual Conventions Used in This Manual ........................... x For More Information ...................................... xii Chapter 1 Magazine Layout and Pagination Magazine Production .....................................
  • An XML Model of CSS3 As an XƎL ATEX-TEXML-HTML5 Stylesheet

    An XML Model of CSS3 As an XƎL ATEX-TEXML-HTML5 Stylesheet

    An XML model of CSS3 as an XƎLATEX-TEXML-HTML5 stylesheet language S. Sankar, S. Mahalakshmi and L. Ganesh TNQ Books and Journals Chennai Abstract HTML5[1] and CSS3[2] are popular languages of choice for Web development. However, HTML and CSS are prone to errors and difficult to port, so we propose an XML version of CSS that can be used as a standard for creating stylesheets and tem- plates across different platforms and pagination systems. XƎLATEX[3] and TEXML[4] are some examples of XML that are close in spirit to TEX that can benefit from such an approach. Modern TEX systems like XƎTEX and LuaTEX[5] use simplified fontspec macros to create stylesheets and templates. We use XSLT to create mappings from this XML-stylesheet language to fontspec-based TEX templates and also to CSS3. We also provide user-friendly interfaces for the creation of such an XML stylesheet. Style pattern comparison with Open Office and CSS Now a days, most of the modern applications have implemented an XML package format that includes an XML implementation of stylesheet: InDesign has its own IDML[6] (InDesign Markup Language) XML package format and MS Word has its own OOXML[7] format, which is another ISO standard format. As they say ironically, the nice thing about standards is that there are plenty of them to choose from. However, instead of creating one more non-standard format, we will be looking to see how we can operate closely with current standards. Below is a sample code derived from OpenOffice document format: <style:style style:name=”Heading_20_1” style:display-name=”Heading
  • Seven Steps to Regulatory Publication Style with Proc Report Dennis Gianneschi, Amgen Inc., Thousand Oaks, CA

    Seven Steps to Regulatory Publication Style with Proc Report Dennis Gianneschi, Amgen Inc., Thousand Oaks, CA

    Seven Steps to Regulatory Publication Style With Proc Report Dennis Gianneschi, Amgen Inc., Thousand Oaks, CA ABSTRACT This paper outlines SAS® 9.1.3 coding steps to produce output that meets "Regulatory Publication Style". This style is specific to my clinical trial reporting environment and is composed of requirements coming from two separate sources. The first source is an internal company document called the Style Guide for Regulatory Submission, which all output submitted to a regulatory agency must follow. The second source is the publishing software itself, which processes all output into the regulatory filing. Examples of style guide requirements are: RTF output, Arial font, and that footnotes must attach to the bottom of the table without a box drawn around them. Publishing system requirements are: a) The user controls the type of line breaks, either soft, {\line}, or hard, {\par}, in the title, which controls how much of the title is picked up by the publishing software and put in the table of contents. b) Each line, such as a spanning underline or the line between the table body and the footnotes, must have a minimum thickness of 19 twips. c) Section breaks are not allowed. d) Table title and footnotes cannot be in the header or footnote section of the RTF document. e) Table title must be "free text" on the page and not in a table structure. The seven steps to achieve this style are: 1) proc template, 2) statistical procs (optional), 3) reformat data (optional), 4) add pagination and footnotes, 5) proc report, 6) post process RTF file, and 7) View in WORD® (optional).
  • NOVEMBER 18 • WEDNESDAY Build Stuff'15 Lithuania

    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.
  • The Best of Both Worlds?

    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.
  • Book Typography 101 at the End of This Session, Participants Should Be Able To: 1

    Book Typography 101 at the End of This Session, Participants Should Be Able To: 1

    3/21/2016 Objectives Book Typography 101 At the end of this session, participants should be able to: 1. Evaluate typeset pages for adherence Dick Margulis to traditional standards of good composition 2. Make sensible design recommendations to clients based on readability of text and clarity of communication © 2013–2016 Dick Margulis Creative Services © 2013–2016 Dick Margulis Creative Services What is typography? Typography encompasses • The design and layout of the printed or virtual page • The selection of fonts • The specification of typesetting variables • The actual composition of text © 2013–2016 Dick Margulis Creative Services © 2013–2016 Dick Margulis Creative Services What is typography? What is typography? The goal of good typography is to allow Typography that intrudes its own cleverness the unencumbered communication and interferes with the dialogue of the author’s meaning to the reader. between author and reader is almost always inappropriate. Assigned reading: “The Crystal Goblet,” by Beatrice Ward http://www.arts.ucsb.edu/faculty/reese/classes/artistsbooks/Beatrice%20Warde,%20The%20Crystal%20Goblet.pdf (or just google it) © 2013–2016 Dick Margulis Creative Services © 2013–2016 Dick Margulis Creative Services 1 3/21/2016 How we read The basics • Saccades • Page size and margins The quick brown fox jumps over the lazy dog. Mary had a little lamb, a little bread, a little jam. • Line length and leading • Boules • Justification My very educated mother just served us nine. • Typeface My very educated mother just served us nine.
  • On the Cognitive Prerequisites of Learning Computer Programming

    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.
  • Handout 16: J Dictionary

    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 <.
  • Figures and Tables

    Figures and Tables

    Word for Research Writing II: Figures and Tables Last updated: 10/2017 ♦ Shari Hill Sweet ♦ [email protected] or 631‐7545 1. The Graduate School Template .................................................................................................. 1 1.1 Document structure ...................................................................................................... 1 1.1.1 Beware of Section Breaks .................................................................................... 1 1.1.2 Order of elements ................................................................................................ 2 1.2 Refresher: The Styles Pane ........................................................................................... 3 1.2.1 Style types and usage ........................................................................................... 3 1.2.2 Modifying text styles ............................................................................................ 4 1.2.3 Creating a new text style ..................................................................................... 4 2. Working with Figures and Tables ................................................................................................ 6 2.1 Figures: Best practices .................................................................................................. 6 2.1.1 Insert figures after the end of a paragraph ......................................................... 6 2.1.2 Order of insertion ...............................................................................................