DOCSLIB.ORG

A Proposed C Language Binding for the Graphical Kernel System-3D

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
A Proposed C Language Binding for the Graphical Kernel System-3D Scholars' Mine Masters Theses Student Theses and Dissertations Fall 1987 A proposed C language binding for the Graphical Kernel System-3D Mark Gerard Bolten Follow this and additional works at: https://scholarsmine.mst.edu/masters_theses Part of the Computer Sciences Commons Department: Recommended Citation Bolten, Mark Gerard, "A proposed C language binding for the Graphical Kernel System-3D" (1987). Masters Theses. 625. https://scholarsmine.mst.edu/masters_theses/625 This thesis is brought to you by Scholars' Mine, a service of the Missouri S&T Library and Learning Resources. This work is protected by U. S. Copyright Law. Unauthorized use including reproduction for redistribution requires the permission of the copyright holder. For more information, please contact [email protected]. A PROPOSED C LANGUAGE BINDING FOR THE GRAPHICAL KERNEL SYSTEM-3D BY MARK GERARD BOLTEN, 1960 - A THESIS Presented to the Faculty of the Graduate School of the UNIVERSITY OF MISSOURI - ROLLA In Partial Fulfillment of the Requirements for the Degree MASTER OF SCIENCE in COMPUTER SCIENCE 1987 Advisor 11 ABSTRACT This thesis introduces a proposed C language binding definition for the International Standards Organization's draft international standard of the Graphical Kernel System-3D. This work augments the earlier C language binding of the two dimensional version of the Graphical Kernel System commonly known as GKS. The proposed function interface will provide a basis for, if not a final, C language binding for the three dimensional version of the Graphical Kernel System. iii ACKNOWLEDGEMENT The author wishes to thank the members of the faculty of the Department of Computer Science at the University of Missouri-Rolla. Their dedication to science and education has produced graduates who are confident of their abilities to approach and solve the problems which will present themselves in industry. It is to those men who have trained, educated, and counselled me that I am professionally indebted to. In particular, I thank the members of the thesis committee which has guided me in my pursuit of the Master of Science in Computer Science: Dr. C. Y. Ho, the thesis committee chairman, and Dr. Arlan DeKock, both of the Department of Computer Science; and Dr. Raymond Kluczny of the Department of Engineering Management. Finally, the author wishes to thank his wife, Mary-Claire, for her understanding and encouragement. iv TABLE OF CONTENTS Page ABSTRACT............................................... ii ACKNOWLEDGEMENT........................................ iii TABLE OF CONTENTS LIST OF TABLES......................................... vii I. INTRODUCTION................................. 1 A. THE EVOLUTION OF COMPUTER GRAPHICS.... 1 B. COMPUTER GRAPHICS STANDARDS............ 4 C. THE GRAPHICAL KERNEL SYSTEM............ 5 II. REVIEW OF LITERATURE........................ 9 A. COMPUTER GRAPHICS...................... 9 B. ORIGINS OF THE GRAPHICAL KERNEL SYSTEM. 10 C. THE GRAPHICAL KERNEL SYSTEM........... 12 D. GKS LANGUAGE BINDINGS.................. 20 III. RESULTS...................................... 21 A. C/GKS-3D NOTATIONAL CONVENTIONS....... 21 B. C/GKS-3D SUBROUTINE DEFINITIONS...... 2 3 1. GKS-3D Control Functions.......... 23 2. GKS-3D Output Functions........... 2 4 3. GKS-3D Output Attribute Functions. 25 4. GKS-3D Transformation Functions... 26 5. GKS-3D Segment Functions......... 27 6. GKS-3D Input Functions............ 2 8 7. GKS-3D Metafile Functions........ 2 9 8. GKS-3D Inquiry Functions.......... 29 9. GKS-3D Utility Functions......... 36 10. GKS-3D Error Functions............ 37 V IV. DISCUSSION............................... 38 A. SCOPE AND FIELD OF APPLICATION.......... 38 B. PRINCIPLES AND FEATURES OF THIS BINDING 39 1. Mapping of GKS Function Names.... 39 2. Parameters........................ 39 3. Error Handling.................... 40 4. Non-Standard C Compiler Support... 41 5. Functions versus Macros.......... 41 6. Character Strings................. 42 7. Function Identifiers.............. 42 8. Registration...................... 42 9. Generalized Drawing Primitives.... 43 10. Escapes........................... 43 11. Header Files...................... 44 12. Error Codes....................... 44 13. Return Values..................... 45 14. Buffer Management................. 45 a. Fixed Structures............ 45 b. Variable Structures......... 46 c. List of Objects.............. 46 V. CONCLUSION.................................. 48 BIBLIOGRAPHY........................................... 50 VITA................................................... 54 APPENDICES............................................. 55 A. ABBREVIATIONS USED IN FUNCTION NAMES........ 55 B. ABBREVIATIONS USED IN DATA TYPE NAMES....... 63 C. DATA TYPES USED IN GKS-3D FUNCTIONS......... 70 D. C/GKS SHORT FUNCTION IDENTIFIERS............ 83 vi E. ORDERED TABLES OF GKS 3D AND 2D FUNCTIONS... 110 F. GKS 3D AND 2D FUNCTIONS ORDERED BY LEVEL--- 140 G. GKS ERROR CODES............................. 162 H. LINE AND MARKER SYMBOLIC CONSTANTS.......... 182 Vll LIST OF TABLES Table Page 1. Workstation Types................................ 8 2. GKS Functional Categories........................ 14 3. GKS Logical Input Classes........................ 17 4. Abbreviations Used in GKS-3D Function Names...... 55 5. Abbreviations Used in GKS-2D Function Names...... 5 6 6. Abbreviations Used in GKS Data Type Names....... 63 7. Short Function Identifiers for GKS-3D Control Functions......................................... 8 3 8. Short Function Identifiers for GKS-3D Output Functions......................................... 84 9. Short Function Identifiers for GKS-3D Output Attributes Functions............................. 8 5 10. Short Function Identifiers for GKS-3D Transfor­ mation Functions 8 6 11. Short Function Identifiers for GKS-3D Segment Functions......................................... 87 12. Short Function Identifiers for GKS-3D Input Functions......................................... 88 13. Short Function Identifiers for GKS-3D Metafile Functions......................................... 89 14. Short Function Identifiers for GKS-3D Inquiry Functions......................................... 90 15. Short Function Identifiers for GKS-3D Utility Functions......................................... 92 16. Short Function Identifiers for GKS-3D Error Functions......................................... 9 3 17. Short Function Identifiers for GKS-2D Control Functions......................................... 94 18. Short Function Identifiers for GKS-2D Output Functions......................................... 9 5 19. Short Function Identifiers for GKS-2D Output Attributes Functions............................. 9 6 viii 20 . Short Function Identifiers for GKS-2D Transfor­ mation Functions.................................. 98 21. Short Function Identifiers for GKS-2D Segment Functions......................................... 99 22. Short Function Identifiers for GKS-2D Input Functions......................................... 100 23. Short Function Identifiers for GKS-2D Metafile Functions......................................... 102 24. Short Function Identifiers for GKS-2D Inquiry Functions......................................... 103 25. Short Function Identifiers for GKS-2D Utility Functions......................................... 108 26. Short Function Identifiers for GKS-2D Error Functions......................................... 109 27. GKS-3D Function Names Ordered by Bound Name..... 110 28. GKS-2D Function Names Ordered by Bound Name..... 115 29. GKS-3D Function Names Ordered by Function Name... 125 30. GKS-2D Function Names Ordered by Function Names.. 130 31. GKS-3D Level 0a Functions......... 140 32. GKS -3D Level 0b Functions........................ 143 33. GKS -3D Level 0c Functions........................ 144 34. GKS -3D Level la Functions........................ 145 35. GKS-3D Level lb Functions........................ 14 6 36. GKS -3D Level 2a Functions........................ 147 37. GKS -2D Level 0a Functions........................ 148 38. GKS-2D Level ob Functions........................ 154 39. GKS-2D Level 0c Functions........................ 156 40. GKS -2D Level la Functions........................ 157 41. GKS-2D Level lb Functions........................ 159 42. GKS-2D Level lc Functions........................ 160 43. GKS-2D Level 2a Functions........................ 161 ix 44. GKS Non-Error Condition Error Code............... 162 45. GKS State Error Codes............................. 163 46. GKS Workstation Error Codes....................... 164 47. GKS Transformation Error Codes................... 166 48. GKS Output Attributes Error Codes................ 167 49. GKS Output Primitives Error Codes................ 17 0 50. GKS Segment Error Codes........................... 171 51. GKS Input Error Codes............................. 172 52. GKS Metafile Error Codes.......................... 173 53. GKS Escape Error Codes............................ 174 54. GKS Miscellaneous Error Codes..................... 175 55. GKS System Error Codes............................ 17 6 56. GKS-3D Transformation Error Codes................ 177 57. GKS-3D Output Attributes Error Codes............. 178 58. GKS -3D Output Primitives Error Codes............. 179 59. GKS C Language Dependent Error Codes............. 180 60. GKS Reserved Error Codes......................... 181 61. Line and Marker Symbolic Constants............... 182 1 I. INTRODUCTION The Graphical Kernel System (GKS) is
Load more

Recommended publications
  • (POSIX®)— Part 1: System Application Program Interface (API) [C Language]
    International Standard ISO/IEC 9945-1: 1996 (E) IEEE Std 1003.1, 1996 Edition (Incorporating ANSI/IEEE Stds 1003.1-1990, 1003.1b-1993, 1003.1c-1995, and 1003.1i-1995) Information technology—Portable Operating System Interface (POSIX®)— Part 1: System Application Program Interface (API) [C Language] Sponsor Portable Applications Standards Committee of the IEEE Computer Society Adopted as an International Standard by the International Organization for Standardization and by the International Electrotechnical Commission Published by The Institute of Electrical and Electronics Engineers, Inc. Abstract: This standard is part of the POSIX series of standards for applications and user interfaces to open systems. It defines the applications interface to basic system services for input/output, file system access, and process management. It also defines a format for data interchange. When options specified in the Realtime Extension are included, the standard also defines interfaces appropriate for realtime applications. When options specified in the Threads Extension are included, the standard also defines interfaces appropriate for multithreaded applications. This standard is stated in terms of its C language binding. Keywords: API, application portability, C (programming language), data processing, information interchange, open systems, operating system, portable application, POSIX, programming language, realtime, system configuration computer interface, threads POSIX is a registered trademark of the Institute of Electrical and Electronics Engineers, Inc. Quote in 8.1.2.3 on Returns is taken from ANSI X3.159-1989, developed under the auspices of the American National Standards Accredited Committee X3 Technical Committee X3J11. The Institute of Electrical and Electronics Engineers, Inc. 345 East 47th Street, New York, NY 10017-2394, USA Copyright © 1996 by the Institute of Electrical and Electronics Engineers, Inc.
    [Show full text]
  • The Glib/GTK+ Development Platform
    The GLib/GTK+ Development Platform A Getting Started Guide Version 0.8 Sébastien Wilmet March 29, 2019 Contents 1 Introduction 3 1.1 License . 3 1.2 Financial Support . 3 1.3 Todo List for this Book and a Quick 2019 Update . 4 1.4 What is GLib and GTK+? . 4 1.5 The GNOME Desktop . 5 1.6 Prerequisites . 6 1.7 Why and When Using the C Language? . 7 1.7.1 Separate the Backend from the Frontend . 7 1.7.2 Other Aspects to Keep in Mind . 8 1.8 Learning Path . 9 1.9 The Development Environment . 10 1.10 Acknowledgments . 10 I GLib, the Core Library 11 2 GLib, the Core Library 12 2.1 Basics . 13 2.1.1 Type Definitions . 13 2.1.2 Frequently Used Macros . 13 2.1.3 Debugging Macros . 14 2.1.4 Memory . 16 2.1.5 String Handling . 18 2.2 Data Structures . 20 2.2.1 Lists . 20 2.2.2 Trees . 24 2.2.3 Hash Tables . 29 2.3 The Main Event Loop . 31 2.4 Other Features . 33 II Object-Oriented Programming in C 35 3 Semi-Object-Oriented Programming in C 37 3.1 Header Example . 37 3.1.1 Project Namespace . 37 3.1.2 Class Namespace . 39 3.1.3 Lowercase, Uppercase or CamelCase? . 39 3.1.4 Include Guard . 39 3.1.5 C++ Support . 39 1 3.1.6 #include . 39 3.1.7 Type Definition . 40 3.1.8 Object Constructor . 40 3.1.9 Object Destructor .
    [Show full text]
  • SVG Tutorial
    SVG Tutorial David Duce *, Ivan Herman +, Bob Hopgood * * Oxford Brookes University, + World Wide Web Consortium Contents ¡ 1. Introduction n 1.1 Images on the Web n 1.2 Supported Image Formats n 1.3 Images are not Computer Graphics n 1.4 Multimedia is not Computer Graphics ¡ 2. Early Vector Graphics on the Web n 2.1 CGM n 2.2 CGM on the Web n 2.3 WebCGM Profile n 2.4 WebCGM Viewers ¡ 3. SVG: An Introduction n 3.1 Scalable Vector Graphics n 3.2 An XML Application n 3.3 Submissions to W3C n 3.4 SVG: an XML Application n 3.5 Getting Started with SVG ¡ 4. Coordinates and Rendering n 4.1 Rectangles and Text n 4.2 Coordinates n 4.3 Rendering Model n 4.4 Rendering Attributes and Styling Properties n 4.5 Following Examples ¡ 5. SVG Drawing Elements n 5.1 Path and Text n 5.2 Path n 5.3 Text n 5.4 Basic Shapes ¡ 6. Grouping n 6.1 Introduction n 6.2 Coordinate Transformations n 6.3 Clipping ¡ 7. Filling n 7.1 Fill Properties n 7.2 Colour n 7.3 Fill Rule n 7.4 Opacity n 7.5 Colour Gradients ¡ 8. Stroking n 8.1 Stroke Properties n 8.2 Width and Style n 8.3 Line Termination and Joining ¡ 9. Text n 9.1 Rendering Text n 9.2 Font Properties n 9.3 Text Properties -- ii -- ¡ 10. Animation n 10.1 Simple Animation n 10.2 How the Animation takes Place n 10.3 Animation along a Path n 10.4 When the Animation takes Place ¡ 11.
    [Show full text]
  • Standards Action Layout SAV3528.Fp5
    PUBLISHED WEEKLY BY THE AMERICAN NATIONAL STANDARDS INSTITUTE 25 West 43rd Street, NY, NY 10036 VOL. 35, #28 July 9, 2004 Contents American National Standards Call for Comment on Standards Proposals ................................................ 2 Call for Comment Contact Information ....................................................... 9 Final Actions.................................................................................................. 11 Project Initiation Notification System (PINS).............................................. 14 International Standards ISO and IEC Newly Published Standards.................................................... 18 Registration of Organization Names in the U.S............................................ 21 Proposed Foreign Government Regulations................................................ 21 Information Concerning ................................................................................. 22 Standards Action is now available via the World Wide Web For your convenience Standards Action can now be down- loaded from the following web address: http://www.ansi.org/news_publications/periodicals/standards _action/standards_action.aspx?menuid=7 American National Standards Call for comment on proposals listed This section solicits public comments on proposed draft new American National Standards, including the national adoption of Ordering Instructions for "Call-for-Comment" Listings ISO and IEC standards as American National Standards, and on 1. Order from the organization indicated for
    [Show full text]
  • The Component Object Model Specification Version 0.9 October 24, 1995
    http://scottge.wordpress.com The Component Object Model Specification Version 0.9 October 24, 1995 This document contains the specification to the Component Object Model (COM), an architecture and supporting infrastructure for building, using, and evolving component software in a robust manner. This specification contains the standard APIs supported by the COM Library, the standard suites of interfaces supported or used by software written in a COM environment, along with the network protocols used by COM in support of distributed computing. This specification is still in draft form, and thus subject to change. Note: This document is an early release of the final specification. It is meant to specify and accompany software that is still in development. Some of the information in this documentation may be inaccurate or may not be an accurate representation of the functionality of the final specification or software. Microsoft assumes no responsibility for any damages that might occur either directly or indirectly from these inaccuracies. Microsoft may have trademarks, copyrights, patents or pending patent applications, or other intellectual property rights covering subject matter in this document. The furnishing of this document does not give you a license to these trademarks, copyrights, patents, or other intellectual property rights. Copyright ? 1992-95 Microsoft Corporation. All Rights Reserved The Component Object Model Specification The Component Object Model The Component Object Model Specification Draft Version 0.9, October 24, 1995 Microsoft Corporation and Digital Equipment Corporation Copyright ? 1992-95 Microsoft Corporation. Microsoft does not make any representation or warranty regarding the Specification or any product or item developed based on the Specification.
    [Show full text]
  • Cad Standards
    ME 6501-CAD MECHANICAL ENGINEERING UNIT - V CAD STANDARDS PART - A 1. List some Standards us ed in computer graphics. 2. What are the Types of Standards used in CAD? • Graphics Standa rds • Data Exchange Standards • Communication Standards 3. Write Aim of Graphics Standardization. • To provide versatility in the combination of Software and Hardware items of turnkey systems • To allow the creation of portable application software package, applicable for wide range of hardware makes enumand configurations 4. Enumerate GKS 3D. ME 6501-CAD MECHANICAL ENGINEERING 5. Write short note on PH IGS. 6. Write short note on NA PLPS. 7. List the features of NAP LPS. 8. Sketch the layer model of GKS. ME 6501-CAD MECHANICAL ENGINEERING 9. Write features of Conti nuous Acquisition and Life-cycle Support (C ALS). •Developed by U S Department of Defense •Prescribes formats for storage and exchange of technical data •Technical publications an important focus 10. Sketch STEP Architect ure. 11. List the Classes of STE P Parts. •Introductory •Description meth ods •Implementation methods •Conformance testing methodology and framework •Integrated resour ces •Application prot ocols •Abstract test suites 12. What are Important CA LS Standards? • Standard Genera lized Markup Language (SGML) • Computer Grap hics Metafile (CGM) 13. Note on Computer Gra phics Metafile (CGM). Devel oped in 1986 vector file format for illustrations and drawings All gra phical elements can be specified in a textual so urce file that can be com piled into a binary file or one of two text repres entations ME 6501-CAD MECHANICAL ENGINEERING 14. What is meant by OpenGL (Open Graphics Library)? OpenGL is a cross-language, multi-platform application programming interface (API) forrendering 2D and 3D vector graphics.
    [Show full text]
  • Design and Implementation of a 2D Graphics Package In
    - DESIGN AND IMPLEMENTATION OF A 2D GRAPHICS PACKAGE IN ADA 95 By LAN LI Bachelor of Science ZheJiang University HangZhou, China 1987 Submitted to the Faculty of the Graduate College of the Oklahoma State University in partial fulfillment of the requirements for the Degree of MASTER OF SCIENCE December, 1996 - DESIGN AND IMPLEMENTATION OF A 2D GRAPHICS PACKAGE IN ADA 95 Thesis approved: H. ~< 11 - ACKNOWLEDGMENT I express my sincere gratitude to my advisor Dr. George for his constructive guidance, supervision, inspiration and financial support. Without his understanding and support, I could not have accomplished this project. Appreciation also extends to my committee members Dr. Chandler and Dr. Lu, their great help are invaluable when I was in difficult situation. I would also like to thank my husband who always gives me encouragement and support in the background. Thanks my son Eric, who was just born, for sharing my happiness and pain, tolerating my occasional inattention during this project. My special thanks also go to my parents who help me take care of my baby with their tremendous love that give me much time to finish this work. This project is supported by DISA Grant DCA 100-96-1-0007 iii L - TABLE OF CONTENTS Chapter Page 1. Introduction 1 2. Literature Review ..............................................................................•.............3 2.1. A Review of Standard Graphics Packages 3 2.1.1. GKS (Graphical Kernel System) 3 a) Logic3.1 Workstations ., 5 b) Graphics Primitives 6 c) logical Input Devices................................................................•...........•.............. 7 d) Mode of Interaction 7 e) Segmentation .....................................................................................•................. 7 f) Metafile '•...........•................................ 8 2.1.2. PHIGS (Programmer's Hierarchical Interactive Graphics System) 8 a) Graphics Output 9 b) Graphics Inpu.t 10 c) Interaction handling .............................................................................•.•........
    [Show full text]
  • A HIGH-LEVEL GRAPHICS LANGUAGE BASED on the GRAPHICAL KERNEL SYSTEM by HANQIU SUN B . a . S C , Huazhong U N I V E R S I T Y
    A HIGH-LEVEL GRAPHICS LANGUAGE BASED ON THE GRAPHICAL KERNEL SYSTEM by HANQIU SUN B.A.Sc, Huazhong University, 1981 A THESIS SUBMITTED IN PARTIAL FULFILMENT OF THE REQUIREMENTS FOR THE DEGREE OF MASTER OF APPLIED SCIENCE in THE FACULTY OF GRADUATE STUDIES Department of Electrical Engineering We accept this thesis as conforming to the required standard THE UNIVERSITY OF BRITISH COLUMBIA February 1986 © Hanqiu Sun, 1986 In presenting this thesis in partial fulfilment of the requirements for an advanced degree at the University of British Columbia, I agree that the Library shall make it freely available for reference and study. I further agree that permission for extensive copying of this thesis for scholarly purposes may be granted by the head of my department or by his or her representatives. It is understood that copying or publication of this thesis for financial gain shall not be allowed without my written permission. Department of Fkcf^''ccv£ (p^r'KA*-'r/<Af The University of British Columbia 1956 Main Mall Vancouver, Canada V6T 1Y3 Date Ma»JL S>o , fIBf >E-6 (3/81) i i Abstract Being an application area of programming languages, graphics languages should keep pace with the development of today's programming languages. Data types, structural operations and free layout of statements provide a more effective means of picture generation, i.e., modelling, rendering and viewing. The Graphical Kernel System (GKS), an international standard graphics language since 1984, is specified on a subroutine basis, therefore suffering from the lack of such high-level language features. This thesis investigates and implements the FORTRAN language binding of GKS into a high-level programming language (HL/GKS) by a generated precompiler.
    [Show full text]
  • Reading for Monday
    Reading for Monday Subsequent pages of this document contain the appropriate excerpts from the 3 papers, in the order of the bullet points listed below: • H/Direct: • Read sections 1 and 2: this sets up the problem and design space. – In section 2.3: focus on understanding IDL types versus Haskell types. • Read the bullets on page 157: these explain the five IDL pointer types. • Attempt to understand what marshalPoint on page 159 is doing. • Take note of the main claim on the page after page 159. • Stretching the storage manager: • Read section 4 to understand stable names and stable pointers – Read section 4.4 closely to understand some garbage collection im- plications. • Read section 5.6 to understand the memory management issue (not the solution). • Calling hell from heaven and heaven from hell: • Read the second bulleted point in the intro. • Read section 3 – Read section 3.3 closely (stable pointers) – Read section 3.5 closely (higher-order callbacks) • The Lua Registry: • Read section 27.3.1: “Lua offers a separate table, called the registry, that C code can freely use, but Lua code cannot access.” 1 H/Direct: A Binary Foreign Language Interface for Haskell Sigbjorn Finne Daan Leijen Erik Meijer University of Glasgow University of Utrecht University of Utrecht [email protected] [email protected] [email protected] Simon Peyton Jones University of Glasgow [email protected] Abstract the particular Haskell implementation. To maintain this in- dependence, H/Direct requires the implementation to sup- H/Direct is a foreign-language interface for the purely func- port a primitive foreign-language interface mechanism, ex- tional language Haskell.
    [Show full text]
  • GKS-94 to SVG: Some Reflections on the Evolution of Standards for 2D
    EG UK Computer Graphics & Visual Computing (2015) Rita Borgo, Cagatay Turkay (Editors) GKS-94 to SVG: Some Reflections on the Evolution of Standards for 2D Graphics D. A. Duce1 and F.R.A. Hopgood2 1Department of Computing and Communication Technologies, Oxford Brookes University, UK 2Retired, UK Abstract Activities to define international standards for computer graphics, in particular through ISO/IEC, started in the 1970s. The advent of the World Wide Web has brought new requirements and opportunities for standardization and now a variety of bodies including ISO/IEC and the World Wide Web Consortium (W3C) promulgate standards in this space. This paper takes a historical look at one of the early ISO/IEC standards for 2D graphics, the Graph- ical Kernel System (GKS) and compares key concepts and approaches in this standard (as revised in 1994) with concepts and approaches in the W3C Recommendation for Scalable Vector Graphics (SVG). The paper reflects on successes as well as lost opportunities. Categories and Subject Descriptors (according to ACM CCS): I.3.6 [Computer Graphics]: Methodology and Techniques—Standards 1. Introduction a W3C Recommendation early in 1999. The current (at the time of writing) revision was published in 2010 [web10]. The Graphical Kernel System (GKS) was the first ISO/IEC international standard for computer graphics and was pub- It was clear from the early days that a vector graphics for- lished in 1985 [GKS85]. This was followed by other stan- mat specifically for the web would be a useful addition to the dards including the Computer Graphics Metafile (CGM), then-available set of markup languages.
    [Show full text]
  • On2 Flix Engine for Linux Installation
    On2 Flix Engine for Linux Installation Topics Preparing the System Java Perl PHP Python Installation Instructions 1. Accept the EULA 2. Verify Prerequisites 3. Uninstall the Previous Version 4. Verify Language Support 5. Register On2 Flix Engine 6. Configure the Installation 7. Install Files 8. Configure the System 9. Build Optional Modules 10. Installation Complete Additional Resources Preparing the System Perform the following to prepare the system for installation: 1. Read the System Overview document provided with this release. 2. Verify Linux prerequisites. a. Operating System: x86 GNU/Linux with GNU C Library (glibc) version 2.3.2 or higher, x86_64 is supported with 32-bit support libraries installed. To determine the version of glibc installed on your system, execute the following: $ /lib/ld-linux.so.2 /lib/libc.so.6 This command should produce output similar to the following (note, your output may differ, however the version number should be equal or greater). © 2009, On2 Technologies, Inc. 1 On2 Flix Engine for Linux Installation GNU C Library stable release version 2.3.2, by Roland McGrath et al. Copyright (C) 2003 Free Software Foundation, Inc. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. Compiled by GNU CC version 3.3.3. Compiled on a Linux 2.4.26 system on 2004-05-24. Available extensions: GNU libio by Per Bothner crypt add-on version 2.1 by Michael Glad and others linuxthreads-0.10 by Xavier Leroy BIND-8.2.3-T5B libthread_db work sponsored by Alpha Processor Inc NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk Report bugs using the `glibcbug' script to <[email protected]>.
    [Show full text]
  • Inferred Interface Glue: Supporting Language Interoperability with Static Analysis
    Inferred Interface Glue: Supporting Language Interoperability with Static Analysis by Tristan Ravitch A dissertation submitted in partial fulfillment of the requirements for the degree of Doctor of Philosophy (Computer Sciences) at the UNIVERSITY OF WISCONSIN–MADISON 2013 Date of final oral examination: 08/09/2013 The dissertation is approved by the following members of the Final Oral Committee: Ben Liblit, Associate Professor, Computer Sciences Tom Reps, Professor, Computer Sciences Susan Horwitz, Professor, Computer Sciences Somesh Jha, Professor, Computer Sciences Timothy Tautges, Adjunct Professor, Engineering Physics © Copyright by Tristan Ravitch 2013 All Rights Reserved i acknowledgments I would like to thank Aditya Thakur, Tycho Andersen, Evan Driscoll, and Steve Jackson for many productive technical discussions and valuable feedback for both practice talks and paper submissions. I would also like to thank my advisor Ben Liblit for consistent encouragement and support. Most importantly, I thank Tycho Andersen, Polina Dudnik, James Doherty, Aubrey Barnard, Erin Barnard, and Bess Berg for numerous bicycle rides and the many other things that have made Madison enjoyable. ii contents Contents ii List of Tables iv List of Figures v Abstract viii 1 Introduction 1 1.1 Preliminaries 6 2 Related Work 8 2.1 Library Binding Generation 8 2.2 FFI Checking 10 3 Error Codes 12 3.1 Algorithm 14 3.2 Related Work 30 3.3 Evaluation 31 4 Semantics of Pointer Parameters 43 4.1 Symbolic Access Paths 48 4.2 Array Parameters 50 4.3 Output Parameters 51
    [Show full text]