C/C++ Compiler V1.0 (Reliant UNIX)

Total Page:16

File Type:pdf, Size:1020Kb

C/C++ Compiler V1.0 (Reliant UNIX) 1 Preface The C/C++ compiler described in this manual is a native compiler that supports the C and C++ programming languages. This compiler can be called and controlled by means of the following commands: cc, c89 The compiler works as a C compiler. CC The compiler works as a C++ compiler. The C/C++ compiler is a part of the C/C++ development system CDS++, which is an independent software package from the Reliant UNIX base system. CDS++ includes not only the C/C++ compiler, but also the symbolic debugging aid DBX and various C++ libraries (i.e. the Cfront-compatible library, the standard C++ library and Tools.h++). In order to use CDS++, you will also need the C libraries, headers and tools from the ccs, attlib, atthead, ucblib, ucbhead, ucbcmd and attcmd packages. These packages are part of the Reliant UNIX base system. Depending on which license is purchased, the C/C++ compiler can be used as only a C compiler (with the “CDS” license) or as both a C and C++ compiler (with the “CDS++” license). See the Release Notice for further details. U25438-J-Z145-1-7600 1 Documentation for CDS++ and additional references Preface 1.1 Documentation for CDS++ and additional references The following important manuals and reference literature are available for developing C and C++ programs using CDS++ and other software components of the Reliant UNIX system: Manuals that can be ordered from SNI – This “C/C++ Compiler” User Guide See the “Summary of contents” in the next section. – “Reliant UNIX, Programmer´s Reference Manual” C library functions, system calls and commands for program development (e.g. ld, sccs, yacc) – “DBX V2.3”, User Guide Symbolic Debugger for C, C++ and FORTRAN – “Standard C++ Library V1.2”, User´s Guide and Reference Rogue Wave manual for the ANSI C++ libraries Strings, Containers, Iterators, Algorithms and Numerics – “Tools.h++ V7.0”, User´s Guide and “Tools.h++ V7.0”, Class Reference Rogue Wave manuals for the widespread and commonly usable C++ class libraries – “Cfront C++ Library”, Reference Manual Classes, functions and operators for complex math and stream-oriented I/O (compatible to Cfront V3.0.3) Documentation supplied with CDS++ – “C++ Language Addendum” (see the Release Notice for details on the delivery format). This document contains ANSI C++ language elements which have not been defined in the C++ language definition by Bjarne Stroustrup (2nd. edition) or which deviate from it. – Release Notice. The Release Notice (readme file) is a part of the CDS++ Readme package. It contains important information and the latest amendments related to the product, its use (especially on older SINIX V5.42 systems), and the supplied manuals. 2 U25438-J-Z145-1-7600 Preface Documentation for CDS++ and additional references Other reference literature and standards – “The C Programing Language 2nd Edition - ANSI-C”, by B.W. Kernighan and D.M. Ritchie, Prentice Hall, ISBN 0-13-110370-9 Introduction to C, problem-oriented description of the C language elements with a large number of examples, reference section (C language description), C solution. – “The C++ Programming Language, 2nd Edition”, by Bjarne Stroustrup, Addison- Wesley, 1991, ISBN 0-201-53992-6 Introduction to C and C++ with a large number of examples, three chapters on software development using C++ and a complete reference manual. – “American National Standard for Information Systems - Programming Language C”, Doc.No. X3J11/90-013, February 14, 1990 or “International Standard ISO/IEC 9899 : 1990, Programming languages - C” – “International Standard ISO/IEC 9899 : 1990, Programming languages - C / Amendment 1 : 1994” – “System Application Binary Interface, MIPS Processor supplement”, Prentice Hall, ISBN 0-13-880170-3 – “Working Paper for Draft Proposed International Standard for Information Systems - Programming Language C++”, Doc.No. X3J16/96-0219R1, WG21/N0137, Dec 2 1996 This document can be ordered from: American National Standards Institute (ANSI), Standards Secretariat: ITIC, 1250 Eye Street NW, Suite 200, Washington DC 20005 USA) or from: Normenausschuß Informationstechnik im DIN Deutsches Institut für Normung e.V. 10772 Berlin U25438-J-Z145-1-7600 3 Summary of contents Preface 1.2 Summary of contents This User Guide is indented for C and C++ programmers. It describes how C and C++ programs can be compiled with the C/C++ compiler and then be linked and executed. In order to work effectively with this manual, you will need to be familiar with the C and C++ programming languages and the Reliant UNIX operating system. Following this preface, you will find an overview of the C/C++ Development System and its components described in chapter 2. The commands to call the compiler are cc, c89 and CC. These commands are described in detail with their possible options and effects in chapter 3. Chapter 4 describes how headers can be precompiled. Chapter 5 describes how programs can be optimized. Chapter 6 describes how the link editor works and how you can create and use libraries. Chapters 7 and 8 deal with extensions to the C and C++ language definitions and describe the implementation and machine-dependent language features of this compiler. Chapter 9 (the appendix) contains an alphabetically-ordered list of all compiler options with references to the pages on which they are described. 4 U25438-J-Z145-1-7600 Preface Notational conventions 1.3 Notational conventions The following notational conventions are used to depict commands, options and program statements described in this User Guide: -B dynamic Uppercase letters, digits and special characters in typewritten text are constants and must be entered exactly as shown, except for the arguments for the -K option, which are shown in the manual in lowercase letters, but may be entered in both uppercase and lowercase (see page 23). name Lowercase letters in italics denote variables, which must be replaced by current values at the time of input. {cc | c89} Braces enclose alternatives from which one must be selected. The separator character | must not be specified. [ ] Square brackets enclose options that may be omitted. ( ) Parentheses are constants and must be specified. Ë This symbol indicates that at least one white space character is necessary for the syntax. ... Ellipses signify repetition, i.e. the preceding unit can be repeated several times in succession. U25438-J-Z145-1-7600 5 Eine Dokuschablone von Frank Flachenecker by f.f. 1992 2 The C/C++ development system The C/C++ development system CDS++ essentially consists of the following components: – the C/C++ compiler – extensive C++ libraries and runtime systems – the symbolic debugger DBX This chapter provides an overview of these components and their most important charac- teristics. Detailed information on the C/C++ compiler can be found in the remaining chapters of this manual. For information on the various C++ libraries and the symbolic debugger DBX, see the manuals listed under the Documentation section. U25438-J-Z145-1-7600 7 The C/C++ compiler The C/C++ development system 2.1 The C/C++ compiler 2.1.1 General characteristics Supported C and C++ language standards The compiler supports the following C and C++ language standards: – ANSI/ISO C with the ISO C Addendum 1 (1994) – the status of the ANSI C++ draft from early 1996 including, in particular, exception handling, templates, new-style casts, name spaces, runtime type information (RTTI), etc. Controlling the compiler Three commands are available to call and control the compiler: cc, c89 and CC. The call syntax for these commands is based on the definition in the XPG4 standard. cc, c89 The compiler operates as a C compiler and optionally supports the Kernighan & Ritchie C, extended ANSI/ISO C (default for the cc command) and strict ANSI/ISO C (default for the c89 command) modes. CC The compiler operates as a C++ compiler and optionally supports the Cfront V3.0.3-compatible C++, extended ANSI/ISO C++ (default) and strict ANSI/ISO C++ modes. The cc, c89 and CC commands to call the compiler also include an integrated linkage phase with which compiled objects can be linked into an executable file or a shared library. Compatibility The following language modes are offered by the compiler to enable the migration or porting of older C and C++ applications: Kernighan&Ritchie C, Cfront C++ V3.0.3, preprocessor dialects based on Reiser’s cpp and Johnson’s pcc. Portable software To develop portable software, the compiler also supports the “strict” ANSI C and ANSI C++ modes. All deviations from the corresponding language standards are diagnosed in these modes. 8 U25438-J-Z145-1-7600 The C/C++ development system The C/C++ compiler 64-bit data model A new 64-bit data model that supports pointers and integers with a length of 64 bits (see Release Notice) is now available in addition to the 32-bit API. High optimization In order to produce applications with maximum runtime performance, a number of effective optimization techniques ranging from simple optimization to complex cross-module feedback optimization have been implemented in the compiler. Native C++ compiler In contrast to C++ V3.0, which generated C code from C++ code and passed it to the C compiler, CDS++ directly generates object code in ELF format from C++ code. Precompilation of headers In order to reduce the compilation time when compiling a source file, the compiler can store the compiled code of header files in a separate file and then reuse the precompiled header on compiling the same or any other source file. Thread support The compiler and the C++ libraries support threaded programs with the Thread package of the product DCE (Reliant UNIX) V2.0. makefile dependencies The compiler optionally generates file dependencies (with the -M option) that can be used as input for the UNIX program make.
Recommended publications
  • Mipspro C++ Programmer's Guide
    MIPSproTM C++ Programmer’s Guide 007–0704–150 CONTRIBUTORS Rewritten in 2002 by Jean Wilson with engineering support from John Wilkinson and editing support from Susan Wilkening. COPYRIGHT Copyright © 1995, 1999, 2002 - 2003 Silicon Graphics, Inc. All rights reserved; provided portions may be copyright in third parties, as indicated elsewhere herein. No permission is granted to copy, distribute, or create derivative works from the contents of this electronic documentation in any manner, in whole or in part, without the prior written permission of Silicon Graphics, Inc. LIMITED RIGHTS LEGEND The electronic (software) version of this document was developed at private expense; if acquired under an agreement with the USA government or any contractor thereto, it is acquired as "commercial computer software" subject to the provisions of its applicable license agreement, as specified in (a) 48 CFR 12.212 of the FAR; or, if acquired for Department of Defense units, (b) 48 CFR 227-7202 of the DoD FAR Supplement; or sections succeeding thereto. Contractor/manufacturer is Silicon Graphics, Inc., 1600 Amphitheatre Pkwy 2E, Mountain View, CA 94043-1351. TRADEMARKS AND ATTRIBUTIONS Silicon Graphics, SGI, the SGI logo, IRIX, O2, Octane, and Origin are registered trademarks and OpenMP and ProDev are trademarks of Silicon Graphics, Inc. in the United States and/or other countries worldwide. MIPS, MIPS I, MIPS II, MIPS III, MIPS IV, R2000, R3000, R4000, R4400, R4600, R5000, and R8000 are registered or unregistered trademarks and MIPSpro, R10000, R12000, R1400 are trademarks of MIPS Technologies, Inc., used under license by Silicon Graphics, Inc. Portions of this publication may have been derived from the OpenMP Language Application Program Interface Specification.
    [Show full text]
  • CRTE V11.1A Common Runtime Environment
    English FUJITSU Software BS2000 CRTE V11.1A Common Runtime Environment User Guide * Edition December 2019 Comments… Suggestions… Corrections… The User Documentation Department would like to know your opinion on this manual. Your feedback helps us to optimize our documentation to suit your individual needs. Feel free to send us your comments by e-mail to: [email protected] senden. Certified documentation according to DIN EN ISO 9001:2015 To ensure a consistently high quality standard and user-friendliness, this documentation was created to meet the regulations of a quality management system which complies with the requirements of the standard DIN EN ISO 9001:2015 . Copyright and Trademarks Copyright © 2019 Fujitsu Technology Solutions GmbH. All rights reserved. Delivery subject to availability; right of technical modifications reserved. All hardware and software names used are trademarks of their respective manufacturers. Table of Contents CRTE V11.1 . 6 1 Preface . 7 1.1 Objectives and target groups of this manual . 8 1.2 Summary of contents . 9 1.3 Changes since the last edition of the manual . 10 1.4 Notational conventions . 11 2 Selectable unit, installation and shareability of CRTE . 12 2.1 CRTE V11.1A selectable unit . 13 2.2 Installing CRTE . 16 2.2.1 CRTE libraries for installation without version specification . 17 2.2.2 Standard installation under the user ID “$.” . 18 2.2.3 Installing with IMON under a non-standard user ID . 19 2.2.4 Installing header files and POSIX link switches in the default POSIX directory . 20 2.2.5 Installing header files and POSIX link switches in any POSIX directory .
    [Show full text]
  • C++ Programmer's Guide
    C++ Programmer’s Guide Document Number 007–0704–130 St. Peter’s Basilica image courtesy of ENEL SpA and InfoByte SpA. Disk Thrower image courtesy of Xavier Berenguer, Animatica. Copyright © 1995, 1999 Silicon Graphics, Inc. All Rights Reserved. This document or parts thereof may not be reproduced in any form unless permitted by contract or by written permission of Silicon Graphics, Inc. LIMITED AND RESTRICTED RIGHTS LEGEND Use, duplication, or disclosure by the Government is subject to restrictions as set forth in the Rights in Data clause at FAR 52.227-14 and/or in similar or successor clauses in the FAR, or in the DOD, DOE or NASA FAR Supplements. Unpublished rights reserved under the Copyright Laws of the United States. Contractor/manufacturer is Silicon Graphics, Inc., 1600 Amphitheatre Pkwy., Mountain View, CA 94043-1351. Autotasking, CF77, CRAY, Cray Ada, CraySoft, CRAY Y-MP, CRAY-1, CRInform, CRI/TurboKiva, HSX, LibSci, MPP Apprentice, SSD, SUPERCLUSTER, UNICOS, X-MP EA, and UNICOS/mk are federally registered trademarks and Because no workstation is an island, CCI, CCMT, CF90, CFT, CFT2, CFT77, ConCurrent Maintenance Tools, COS, Cray Animation Theater, CRAY APP, CRAY C90, CRAY C90D, Cray C++ Compiling System, CrayDoc, CRAY EL, CRAY J90, CRAY J90se, CrayLink, Cray NQS, Cray/REELlibrarian, CRAY S-MP, CRAY SSD-T90, CRAY SV1, CRAY T90, CRAY T3D, CRAY T3E, CrayTutor, CRAY X-MP, CRAY XMS, CRAY-2, CSIM, CVT, Delivering the power . ., DGauss, Docview, EMDS, GigaRing, HEXAR, IOS, ND Series Network Disk Array, Network Queuing Environment, Network Queuing Tools, OLNET, RQS, SEGLDR, SMARTE, SUPERLINK, System Maintenance and Remote Testing Environment, Trusted UNICOS, and UNICOS MAX are trademarks of Cray Research, Inc., a wholly owned subsidiary of Silicon Graphics, Inc.
    [Show full text]
  • A Customizable, Front-End Retargetablesource Code Analysis
    GENOA - A Customizable, front-end retargetable Source Code Analysis Framework Premkumar T. Devanbu [email protected] Dept. Of Computer Science, University of California, Davis, CA 95616 Code Analysis tools provide support for such software engineering tasks as program understanding, software metrics, testing and re-engineering. In this paper we describe genoa, the framework underlying application generators such as Aria [Devanbu et al. 1996] and gen++ [?] which have been used to generate a wide range of practical code analysis tools. This experience illustrates front-end retargetability of genoa; we describe the features of the genoa framework that allow it to be used with dierent front ends. While permitting arbitrary parse tree computations, the genoa specication language has special, compact iteration operators that are tuned for expressing simple, polynomial time analysis programs; in fact, there is a useful sublanguage of the genoa language that can express precisely all (and only) polynomial time (PTIME) analysis programs on parse-trees. Thus, we argue that the genoa language is a simple and convenient vehicle for implementing a range of analysis tools. We also argue that the “front-end reuse” approach of GENOA oers an important advantage for tools aimed at large software projects: the reuse of complex, expensive build procedures to run generated tools over large source bases. In this paper, we describe the genoa framework and our experiences with it. Categories and Subject Descriptors: D.2.3 [Software Engineering]: Coding Tools and Tech- niques; D.2.6 [Software Engineering]: Programming Environments General Terms: Languages Additional Key Words and Phrases: source analysis, reverse engineering, metrics, code inspection 1.
    [Show full text]
  • A History of C++: 1979− 1991
    A History of C++: 1979−1991 Bjarne Stroustrup AT&T Bell Laboratories Murray Hill, New Jersey 07974 ABSTRACT This paper outlines the history of the C++ programming language. The emphasis is on the ideas, constraints, and people that shaped the language, rather than the minutiae of language features. Key design decisions relating to language features are discussed, but the focus is on the overall design goals and practical constraints. The evolution of C++ is traced from C with Classes to the current ANSI and ISO standards work and the explosion of use, interest, commercial activity, compilers, tools, environments, and libraries. 1 Introduction C++ was designed to provide Simula’s facilities for program organization together with C’s effi- ciency and flexibility for systems programming. It was intended to deliver that to real projects within half a year of the idea. It succeeded. At the time, I realized neither the modesty nor the preposterousness of that goal. The goal was modest in that it did not involve innovation, and preposterous in both its time scale and its Draco- nian demands on efficiency and flexibility. While a modest amount of innovation did emerge over the years, efficiency and flexibility have been maintained without compromise. While the goals for C++ have been refined, elaborated, and made more explicit over the years, C++ as used today directly reflects its original aims. This paper is organized in roughly chronological order: §2 C with Classes: 1979– 1983. This section describes the fundamental design decisions for C++ as they were made for C++’s immediate predecessor. §3 From C with Classes to C++: 1982– 1985.
    [Show full text]
  • Reference Guide for Openpower Cpus
    REFERENCE GUIDE FOR OPENPOWER CPUS Version 2020 TABLE OF CONTENTS Preface............................................................................................................. ix Audience Description.......................................................................................... ix Compatibility and Conformance to Standards............................................................ ix Organization..................................................................................................... x Hardware and Software Constraints........................................................................ xi Conventions..................................................................................................... xi Terms............................................................................................................ xii Related Publications......................................................................................... xiii Chapter 1. Fortran, C, and C++ Data Types................................................................ 1 1.1. Fortran Data Types....................................................................................... 1 1.1.1. Fortran Scalars.......................................................................................1 1.1.2. FORTRAN real(2).....................................................................................3 1.1.3. FORTRAN Aggregate Data Type Extensions...................................................... 3 1.1.4. Fortran 90 Aggregate Data Types
    [Show full text]
  • (R)Evolution of C++ Aka the Hitchhiker’S Guide to C++
    C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary (R)evolution of C++ aka The Hitchhiker’s Guide to C++ Łukasz Ziobron´ [email protected] http://ziobron.net code::dive, 2016-11-15 C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary (R)evolution of JS C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author C with Classes Cfront era Standardization time C++ future (R)evolution! Language popularity Summary About the author Interests: Archery Digital photography Machine learning Image processing High tech Starcraft Blogging at ziobron.net 2 C++ is even more popular now, because of
    [Show full text]
  • HP Ac++ Online Programmer's Guide Command Line Options
    HP aC++ Online Programmer's Guide © Copyright 1996, 1997, 1998, 1999 Hewlett-Packard Company All rights reserved. Send mail to report errors or comment on the documentation. Welcome to the HP aC++ Online Programmer's Guide. The guide is divided into the following files. String search is available within each file. (Choose Edit, then Find.) Note that each file may contain links to related topics in other files. Command-Line Options What's New - including release notes for this Command Syntax and Environment version of HP aC++ Variables Diagnostic Messages Information Map - where to find more Distributing Your HP aC++ Products information about this guide and about C++ Exception Handling Getting Started Glossary LEX and YACC with HP aC++ Libraries HP C++ (cfront) to HP aC++ Migration Mixing HP aC++ with Other Languages Guide Optimizing Your Code Pragmas Rogue Wave Library Reference Manuals Precompiled Header Files Preprocessing Rogue Wave Tools.h++ Version 7.0.6 Reference Standardizing Your Code Manual Templates Introduction and Overview Rogue Wave Standard C++ Library Version 1.2.1 Detailed Information Reference Manual Threads NOTE: If you are accessing this guide from the World Wide Web URL, http://docs.hp.com, rather than from a system on which HP aC++ is installed, Rogue Wave documentation is not available. The above two links and any other such links within this guide will not succeed. Command Line Options You can specify command-line options to the aCC command. They allow you to override the default actions of the compiler. Each option begins with either a - or a + sign.
    [Show full text]
  • Cray C and C++ Reference Manual
    Cray C and C++ Reference Manual (8.7) S-2179 Contents Contents 1 About the Cray and C++ Reference Manual...........................................................................................................4 2 The Cray Compiling Environment...........................................................................................................................5 3 Invoke the C and C++ Compilers............................................................................................................................7 4 Compiler Command Line Options.........................................................................................................................12 4.1 Standard Language Conformance Options............................................................................................. 12 4.2 C Specific Language Conformance Options........................................................................................... 15 4.3 C++ Specific Language Conformance Options....................................................................................... 15 4.4 Miscellaneous C++ Specific Options....................................................................................................... 17 4.5 General Language Options..................................................................................................................... 18 4.6 General Optimization Options................................................................................................................. 21 4.7 Cache Management Options...................................................................................................................26
    [Show full text]
  • C/C++ Reference Manual
    C/C++ Reference Manual 0890497-040 July 2004 Copyright 2004 by Concurrent Computer Corporation. All rights reserved. This publication or any part thereof is intended for use with Concurrent Computer Corporation products by Concurrent Computer Corporation personnel, customers, and end–users. It may not be reproduced in any form without the written permission of the publisher. The information contained in this document is believed to be correct at the time of publication. It is subject to change without notice. Concurrent Computer Corporation makes no warranties, expressed or implied, concerning the information contained in this document. To report an error or comment on a specific portion of the manual, photocopy the page in question and mark the correction or comment on the copy. Mail the copy (and any additional comments) to Concurrent Computer Corpora- tion, 2881 Gateway Drive Pompano Beach FL 33069. Mark the envelope “Attention: Publications Department.” This publication may not be reproduced for any other reason in any form without written permission of the publisher. Acknowledgment: This manual contains material contributed by Edison Design Group, Inc. Those portions are copyrighted and reproduced with permission. The license management portion of this product is based on: Élan License Manager Copyright 1989-1993 Elan Computer Group, Inc. All rights reserved. Élan License Manager is a trademark of Élan Computer Group, Inc. NightView and PowerMAX OS are trademarks of Concurrent Computer Corporation. POSIX is a trademark of the Institute of Electrical and Electronics Engineers, Inc. IBM and Power PC are trademarks of IBM Corp. UNIX is a registered trademark licensed exclusively by the X/Open Company Ltd.
    [Show full text]
  • Mincpp: Efficient, Portable Compilation of C Programs
    Mincpp: Efficient, Portable Compilation of C Programs George Moberly B.S., Boston University A thesis submitted to the faculty of the Oregon Graduate Institute of Science & Technology in partial fulfillment of the requirements for the degree Master of Science in Computer Science April, 1994 The thesis "Mincpp:Efficient, Port; le Compilation of C Programs" by George Moberly has been examined and approved b: the following Examination Committee: .-------------______--s---------------------- a Sheard, Ph.D. 1 sistant Professor The s Research Advisor eve Otto, Ph.D. sistant Professor Acknowledgment This thesis and supporting degree program was made possible only with the financial, intellectual, and emotional support of many corporations, institutions, and individuals. Past and present employers Digital Equipment Corporation, Mentor Graphics Corporation, and SpaceLabs Medical, Incorporated generously paid for the vast majority of the educational expenses involved, and have actively supported my work. Degree credit was transferred from Tufts University, The University of Washington, and Oregon State University. The following individuals shared generously of their time to discuss issues with me: Phil Brooks and Mike Gresham of Mentor Graphics, Bill Bregar of Oregon State University, Aki Fujimura of Pure Software, Greg Kostal, Jeff Small, and of course Tim Sheard and Steve Otto of OGI. Finally, my wife Julie deserves profound credit and thanks for not letting me give up when it would have been easier to have done so, and for unwavering belief
    [Show full text]
  • Exception Handling 1 Exception Handling
    Exception handling 1 Exception handling Exception handling is a programming language construct or computer hardware mechanism designed to handle the occurrence of exceptions, special conditions that change the normal flow of program execution. Programming languages differ considerably in their support for exception handling (as distinct from error checking, which is normal program flow that codes for responses to contingencies such as unsuccessful termination of invoked operations). In some programming languages there are functions which cannot be safely called on invalid input data or functions which return values which cannot be distinguished from exceptions. For example, in C the atoi (ASCII to integer conversion) function may return 0 (zero) for any input that cannot be parsed into a valid value. In such languages the programmer must either perform error checking (possibly through some auxiliary global variable such as C's errno) or input validation (perhaps using regular expressions). The degree to which such explicit validation and error checking is necessary is in contrast to exception handling support provided by any given programming environment. Hardware exception handling differs somewhat from the support provided by software tools, but similar concepts and terminology are prevalent. In general, an exception is handled (resolved) by saving the current state of execution in a predefined place and switching the execution to a specific subroutine known as an exception handler. Depending on the situation, the handler may later resume the execution at the original location using the saved information. For example, a page fault will usually allow the program to be resumed, while a division by zero might not be resolvable transparently.
    [Show full text]