DOCSLIB.ORG

GNAT User's Guide for Native Platforms

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
GNAT User's Guide for Native Platforms GNAT User's Guide for Native Platforms GNAT User's Guide for Native Platforms , November 18, 2015 AdaCore Copyright c 2008-2016, Free Software Foundation i Table of Contents 1 About This Guide :::::::::::::::::::::::::::::: 2 1.1 What This Guide Contains ::::::::::::::::::::::::::::::::::::: 2 1.2 What You Should Know before Reading This Guide :::::::::::: 2 1.3 Related Information :::::::::::::::::::::::::::::::::::::::::::: 3 1.4 A Note to Readers of Previous Versions of the Manual :::::::::: 3 1.5 Conventions:::::::::::::::::::::::::::::::::::::::::::::::::::: 4 2 Getting Started with GNAT ::::::::::::::::::: 5 2.1 Running GNAT :::::::::::::::::::::::::::::::::::::::::::::::: 5 2.2 Running a Simple Ada Program :::::::::::::::::::::::::::::::: 5 2.3 Running a Program with Multiple Units :::::::::::::::::::::::: 6 2.4 Using the gnatmake Utility ::::::::::::::::::::::::::::::::::::: 7 3 The GNAT Compilation Model ::::::::::::::: 9 3.1 Source Representation:::::::::::::::::::::::::::::::::::::::::: 9 3.2 Foreign Language Representation:::::::::::::::::::::::::::::: 10 3.2.1 Latin-1::::::::::::::::::::::::::::::::::::::::::::::::::: 10 3.2.2 Other 8-Bit Codes:::::::::::::::::::::::::::::::::::::::: 10 3.2.3 Wide Character Encodings ::::::::::::::::::::::::::::::: 11 3.2.4 Wide Wide Character Encodings ::::::::::::::::::::::::: 12 3.3 File Naming Topics and Utilities :::::::::::::::::::::::::::::: 13 3.3.1 File Naming Rules ::::::::::::::::::::::::::::::::::::::: 13 3.3.2 Using Other File Names :::::::::::::::::::::::::::::::::: 14 3.3.3 Alternative File Naming Schemes ::::::::::::::::::::::::: 15 3.3.4 Handling Arbitrary File Naming Conventions with gnatname :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 17 3.3.4.1 Arbitrary File Naming Conventions :::::::::::::::::: 17 3.3.4.2 Running gnatname :::::::::::::::::::::::::::::::::: 17 3.3.4.3 Switches for gnatname :::::::::::::::::::::::::::::: 18 3.3.4.4 Examples of gnatname Usage :::::::::::::::::::::::: 20 3.3.5 File Name Krunching with gnatkr :::::::::::::::::::::::: 20 3.3.5.1 About gnatkr ::::::::::::::::::::::::::::::::::::::: 20 3.3.5.2 Using gnatkr :::::::::::::::::::::::::::::::::::::::: 20 3.3.5.3 Krunching Method :::::::::::::::::::::::::::::::::: 21 3.3.5.4 Examples of gnatkr Usage ::::::::::::::::::::::::::: 22 3.3.6 Renaming Files with gnatchop:::::::::::::::::::::::::::: 22 3.3.6.1 Handling Files with Multiple Units :::::::::::::::::: 22 3.3.6.2 Operating gnatchop in Compilation Mode ::::::::::: 23 3.3.6.3 Command Line for gnatchop::::::::::::::::::::::::: 24 3.3.6.4 Switches for gnatchop ::::::::::::::::::::::::::::::: 25 3.3.6.5 Examples of gnatchop Usage::::::::::::::::::::::::: 26 3.4 Configuration Pragmas :::::::::::::::::::::::::::::::::::::::: 26 ii 3.4.1 Handling of Configuration Pragmas::::::::::::::::::::::: 28 3.4.2 The Configuration Pragmas Files ::::::::::::::::::::::::: 29 3.5 Generating Object Files ::::::::::::::::::::::::::::::::::::::: 29 3.6 Source Dependencies :::::::::::::::::::::::::::::::::::::::::: 30 3.7 The Ada Library Information Files :::::::::::::::::::::::::::: 31 3.8 Binding an Ada Program:::::::::::::::::::::::::::::::::::::: 32 3.9 GNAT and Libraries :::::::::::::::::::::::::::::::::::::::::: 32 3.9.1 Introduction to Libraries in GNAT ::::::::::::::::::::::: 32 3.9.2 General Ada Libraries :::::::::::::::::::::::::::::::::::: 33 3.9.2.1 Building a library ::::::::::::::::::::::::::::::::::: 33 3.9.2.2 Installing a library :::::::::::::::::::::::::::::::::: 35 3.9.2.3 Using a library :::::::::::::::::::::::::::::::::::::: 35 3.9.3 Stand-alone Ada Libraries :::::::::::::::::::::::::::::::: 36 3.9.3.1 Introduction to Stand-alone Libraries :::::::::::::::: 36 3.9.3.2 Building a Stand-alone Library :::::::::::::::::::::: 37 3.9.3.3 Creating a Stand-alone Library to be used in a non-Ada context :::::::::::::::::::::::::::::::::::::::::::::::::: 38 3.9.3.4 Restrictions in Stand-alone Libraries ::::::::::::::::: 40 3.9.4 Rebuilding the GNAT Run-Time Library ::::::::::::::::: 40 3.10 Conditional Compilation ::::::::::::::::::::::::::::::::::::: 40 3.10.1 Modeling Conditional Compilation in Ada ::::::::::::::: 40 3.10.1.1 Use of Boolean Constants :::::::::::::::::::::::::: 41 3.10.1.2 Debugging - A Special Case :::::::::::::::::::::::: 41 3.10.1.3 Conditionalizing Declarations::::::::::::::::::::::: 43 3.10.1.4 Use of Alternative Implementations::::::::::::::::: 44 3.10.1.5 Preprocessing :::::::::::::::::::::::::::::::::::::: 45 3.10.2 Preprocessing with gnatprep :::::::::::::::::::::::::::: 46 3.10.2.1 Preprocessing Symbols ::::::::::::::::::::::::::::: 46 3.10.2.2 Using gnatprep ::::::::::::::::::::::::::::::::::::: 46 3.10.2.3 Switches for gnatprep :::::::::::::::::::::::::::::: 46 3.10.2.4 Form of Definitions File :::::::::::::::::::::::::::: 47 3.10.2.5 Form of Input Text for gnatprep:::::::::::::::::::: 48 3.10.3 Integrated Preprocessing :::::::::::::::::::::::::::::::: 49 3.11 Mixed Language Programming ::::::::::::::::::::::::::::::: 52 3.11.1 Interfacing to C ::::::::::::::::::::::::::::::::::::::::: 52 3.11.2 Calling Conventions ::::::::::::::::::::::::::::::::::::: 55 3.11.3 Building Mixed Ada and C++ Programs :::::::::::::::: 57 3.11.3.1 Interfacing to C++::::::::::::::::::::::::::::::::: 58 3.11.3.2 Linking a Mixed C++ & Ada Program ::::::::::::: 58 3.11.3.3 A Simple Example ::::::::::::::::::::::::::::::::: 59 3.11.3.4 Interfacing with C++ constructors ::::::::::::::::: 62 3.11.3.5 Interfacing with C++ at the Class Level :::::::::::: 64 3.11.4 Generating Ada Bindings for C and C++ headers ::::::: 69 3.11.4.1 Running the Binding Generator :::::::::::::::::::: 69 3.11.4.2 Generating Bindings for C++ Headers:::::::::::::: 70 3.11.4.3 Switches ::::::::::::::::::::::::::::::::::::::::::: 72 3.11.5 Generating C Headers for Ada Specifications :::::::::::: 72 3.11.5.1 Running the C Header Generator ::::::::::::::::::: 73 iii 3.12 GNAT and Other Compilation Models ::::::::::::::::::::::: 74 3.12.1 Comparison between GNAT and C/C++ Compilation Models ::::::::::::::::::::::::::::::::::::::::::::::::::::: 74 3.12.2 Comparison between GNAT and Conventional Ada Library Models ::::::::::::::::::::::::::::::::::::::::::::::::::::: 74 3.13 Using GNAT Files with External Tools ::::::::::::::::::::::: 75 3.13.1 Using Other Utility Programs with GNAT::::::::::::::: 75 3.13.2 The External Symbol Naming Scheme of GNAT ::::::::: 75 4 Building Executable Programs with GNAT :::::::::::::::::::::::::::::::::::::::::::::::: 77 4.1 Building with gnatmake ::::::::::::::::::::::::::::::::::::::: 77 4.1.1 Running gnatmake ::::::::::::::::::::::::::::::::::::::: 77 4.1.2 Switches for gnatmake :::::::::::::::::::::::::::::::::::: 78 4.1.3 Mode Switches for gnatmake ::::::::::::::::::::::::::::: 85 4.1.4 Notes on the Command Line ::::::::::::::::::::::::::::: 86 4.1.5 How gnatmake Works :::::::::::::::::::::::::::::::::::: 87 4.1.6 Examples of gnatmake Usage ::::::::::::::::::::::::::::: 87 4.2 Compiling with gcc ::::::::::::::::::::::::::::::::::::::::::: 88 4.2.1 Compiling Programs ::::::::::::::::::::::::::::::::::::: 88 4.2.2 Search Paths and the Run-Time Library (RTL) ::::::::::: 89 4.2.3 Order of Compilation Issues :::::::::::::::::::::::::::::: 90 4.2.4 Examples :::::::::::::::::::::::::::::::::::::::::::::::: 90 4.3 Compiler Switches :::::::::::::::::::::::::::::::::::::::::::: 91 4.3.1 Alphabetical List of All Switches ::::::::::::::::::::::::: 91 4.3.2 Output and Error Message Control :::::::::::::::::::::: 104 4.3.3 Warning Message Control ::::::::::::::::::::::::::::::: 108 4.3.4 Debugging and Assertion Control:::::::::::::::::::::::: 126 4.3.5 Validity Checking ::::::::::::::::::::::::::::::::::::::: 127 4.3.6 Style Checking :::::::::::::::::::::::::::::::::::::::::: 130 4.3.7 Run-Time Checks ::::::::::::::::::::::::::::::::::::::: 137 4.3.8 Using gcc for Syntax Checking :::::::::::::::::::::::::: 139 4.3.9 Using gcc for Semantic Checking :::::::::::::::::::::::: 139 4.3.10 Compiling Different Versions of Ada:::::::::::::::::::: 140 4.3.11 Character Set Control:::::::::::::::::::::::::::::::::: 141 4.3.12 File Naming Control ::::::::::::::::::::::::::::::::::: 143 4.3.13 Subprogram Inlining Control ::::::::::::::::::::::::::: 143 4.3.14 Auxiliary Output Control :::::::::::::::::::::::::::::: 144 4.3.15 Debugging Control ::::::::::::::::::::::::::::::::::::: 144 4.3.16 Exception Handling Control :::::::::::::::::::::::::::: 148 4.3.17 Units to Sources Mapping Files :::::::::::::::::::::::: 149 4.3.18 Code Generation Control::::::::::::::::::::::::::::::: 149 4.4 Binding with gnatbind ::::::::::::::::::::::::::::::::::::::: 150 4.4.1 Running gnatbind ::::::::::::::::::::::::::::::::::::::: 150 4.4.2 Switches for gnatbind ::::::::::::::::::::::::::::::::::: 151 4.4.2.1 Consistency-Checking Modes ::::::::::::::::::::::: 156 4.4.2.2 Binder Error Message Control :::::::::::::::::::::: 157 4.4.2.3 Elaboration Control :::::::::::::::::::::::::::::::: 158 iv 4.4.2.4 Output Control :::::::::::::::::::::::::::::::::::: 158 4.4.2.5 Dynamic Allocation Control :::::::::::::::::::::::: 159 4.4.2.6 Binding with Non-Ada Main Programs ::::::::::::: 159 4.4.2.7 Binding Programs with No Main Subprogram::::::: 160 4.4.3 Command-Line Access :::::::::::::::::::::::::::::::::: 160 4.4.4 Search Paths for gnatbind ::::::::::::::::::::::::::::::: 161 4.4.5 Examples of gnatbind Usage :::::::::::::::::::::::::::: 161 4.5 Linking with gnatlink :::::::::::::::::::::::::::::::::::::::: 162 4.5.1 Running gnatlink ::::::::::::::::::::::::::::::::::::::: 162 4.5.2
Load more

Recommended publications
  • Cumberland Tech Ref.Book
    Forms Printer 258x/259x Technical Reference DRAFT document - Monday, August 11, 2008 1:59 pm Please note that this is a DRAFT document. More information will be added and a final version will be released at a later date. August 2008 www.lexmark.com Lexmark and Lexmark with diamond design are trademarks of Lexmark International, Inc., registered in the United States and/or other countries. © 2008 Lexmark International, Inc. All rights reserved. 740 West New Circle Road Lexington, Kentucky 40550 Draft document Edition: August 2008 The following paragraph does not apply to any country where such provisions are inconsistent with local law: LEXMARK INTERNATIONAL, INC., PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions; therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in later editions. Improvements or changes in the products or the programs described may be made at any time. Comments about this publication may be addressed to Lexmark International, Inc., Department F95/032-2, 740 West New Circle Road, Lexington, Kentucky 40550, U.S.A. In the United Kingdom and Eire, send to Lexmark International Ltd., Marketing and Services Department, Westhorpe House, Westhorpe, Marlow Bucks SL7 3RQ. Lexmark may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.
    [Show full text]
  • PCL PC-8, Code Page 437 Page 1 of 5 PCL PC-8, Code Page 437
    PCL PC-8, Code Page 437 Page 1 of 5 PCL PC-8, Code Page 437 PCL Symbol Set: 10U Unicode glyph correspondence tables. Contact:[email protected] http://pcl.to -- -- -- -- $90 U00C9 Ê Uppercase e acute $21 U0021 Ë Exclamation $91 U00E6 Ì Lowercase ae diphthong $22 U0022 Í Neutral double quote $92 U00C6 Î Uppercase ae diphthong $23 U0023 Ï Number $93 U00F4 & Lowercase o circumflex $24 U0024 ' Dollar $94 U00F6 ( Lowercase o dieresis $25 U0025 ) Per cent $95 U00F2 * Lowercase o grave $26 U0026 + Ampersand $96 U00FB , Lowercase u circumflex $27 U0027 - Neutral single quote $97 U00F9 . Lowercase u grave $28 U0028 / Left parenthesis $98 U00FF 0 Lowercase y dieresis $29 U0029 1 Right parenthesis $99 U00D6 2 Uppercase o dieresis $2A U002A 3 Asterisk $9A U00DC 4 Uppercase u dieresis $2B U002B 5 Plus $9B U00A2 6 Cent sign $2C U002C 7 Comma, decimal separator $9C U00A3 8 Pound sterling $2D U002D 9 Hyphen $9D U00A5 : Yen sign $2E U002E ; Period, full stop $9E U20A7 < Pesetas $2F U002F = Solidus, slash $9F U0192 > Florin sign $30 U0030 ? Numeral zero $A0 U00E1 ê Lowercase a acute $31 U0031 A Numeral one $A1 U00ED B Lowercase i acute $32 U0032 C Numeral two $A2 U00F3 D Lowercase o acute $33 U0033 E Numeral three $A3 U00FA F Lowercase u acute $34 U0034 G Numeral four $A4 U00F1 H Lowercase n tilde $35 U0035 I Numeral five $A5 U00D1 J Uppercase n tilde $36 U0036 K Numeral six $A6 U00AA L Female ordinal (a) http://www.pclviewer.com (c) RedTitan Technology 2005 PCL PC-8, Code Page 437 Page 2 of 5 $37 U0037 M Numeral seven $A7 U00BA N Male ordinal (o) $38 U0038
    [Show full text]
  • Bitmap Fonts
    .com Bitmap Fonts 1 .com Contents Introduction .................................................................................................................................................. 3 Writing Code to Write Code.......................................................................................................................... 4 Measuring Your Grid ..................................................................................................................................... 5 Converting an Image with PHP ..................................................................................................................... 6 Step 1: Load the Image ............................................................................................................................. 6 Step 2: Scan the Image .............................................................................................................................. 7 Step 3: Save the Header File ..................................................................................................................... 8 The 1602 Character Set ............................................................................................................................... 10 The 1602 Character Map ............................................................................................................................ 11 Converting the Image to Code .................................................................................................................... 12 Conclusion
    [Show full text]
  • User Guide IGP for SIDM Printers
    User Guide IGP for Dot Matrix Printers Mantenimiento Periféricos Informaticos C/Canteras, 15 28860 Paracauellos de Jarama (Madrid) Tel: 00 34 917481604 Web: https://mpi.com.es/ IGP for Dot Matrix Printers User Guide Scope This User Guide is to be considered as an enhancement to the standard documentation of your printer. Hence keep the printer’s standard documentation ready as your particular printer model is pictured in detail. 2 Mantenimiento Periféricos Informaticos C/Canteras, 15 28860 Paracauellos de Jarama (Madrid) Tel: 00 34 917481604 Web: https://mpi.com.es/ Table of Contents Table of Contents Subject Listing SCOPE........................................................................................................................................................... 2 CHAPTER 1: CONTROL PANEL ............................................................................................................ 7 BASIC ELEMENTS ........................................................................................................................................ 7 MENU STRUCTURE ...................................................................................................................................... 8 MENU PARAMETERS.................................................................................................................................... 9 MENU PRINTOUT EXAMPLE....................................................................................................................... 17 WEBPANEL ENHANCEMENTS ...................................................................................................................
    [Show full text]
  • Forms Printer 248X/249X
    Forms Printer 248x/249x Technical Reference October 2000 www.lexmark.com Third Edition (October 2000) The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: LEXMARK INTERNA- TIONAL, INC. PROVIDES THIS PUBLICATION “AS IS” WITHOUT WAR- RANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in later editions of the publication. Improvements and/or changes in the product(s) and/or the program(s) described in this publication may be made at any time. Publications are not stocked at the address given below; requests for publications should be made to your point of purchase. A form for reader's comments is provided at the back of this publication. If the form has been removed, comments may be addressed to Lexmark International, Inc., Department F95/035-3, 740 New Circle Road N.W., Lexington, Kentucky 40511-1876, U.S.A. Lexmark may use or distribute any of the information you sup- ply in any way it believes appropriate without incurring any obligation to you. Lexmark is a trademark of Lexmark International, Inc. Other trademarks are the property of their respective owners. © Copyright Lexmark International, Inc. 1993, 2000. All rights reserved. UNITED STATES GOVERNMENT RESTRICTED RIGHTS This software and documentation are provided with RESTRICTED RIGHTS.
    [Show full text]
  • Windows NLS Considerations Version 2.1
    Windows NLS Considerations version 2.1 Radoslav Rusinov [email protected] Windows NLS Considerations Contents 1. Introduction ............................................................................................................................................... 3 1.1. Windows and Code Pages .................................................................................................................... 3 1.2. CharacterSet ........................................................................................................................................ 3 1.3. Encoding Scheme ................................................................................................................................ 3 1.4. Fonts ................................................................................................................................................... 4 1.5. So Why Are There Different Charactersets? ........................................................................................ 4 1.6. What are the Difference Between 7 bit, 8 bit and Unicode Charactersets? ........................................... 4 2. NLS_LANG .............................................................................................................................................. 4 2.1. Setting the Character Set in NLS_LANG ............................................................................................ 4 2.2. Where is the Character Conversion Done? .........................................................................................
    [Show full text]
  • Extension of VHDL to Support Multiple-Byte Characters
    Extension of VHDL to support multiple-byte characters Kiyoshi Makino Masamichi Kawarabayashi Seiko Instruments Inc. NEC Corporation 6-41-6 Kameido, Koto-ku 1753 Shimonumabe, Nakahara-ku Tokyo 136-8512 Japan Kawasaki, Kanagawa 211-8666 Japan [email protected] [email protected] Abstract Written Japanese is comprised of many kinds of characters. Whereas one-byte is sufficient for the Roman alphabet, two-byte are required to support written Japanese. It should be noted that written Chinese require three-byte. The scope of this paper is not restricted to written Japanese because we should consider the implementation of the standard which covers the major languages using the multiple-byte characters. Currently, VHDL does not support multiple-byte characters. This has proven to be a major impediment to the productivity for electronics designers in Japan, and possibly in other Asian countries. In this paper, we briefly describe the problem, give a short background of the character set required to support Japanese and other multiple-byte characters language, and propose a required change in the IEEE Std 1076. 1. Introduction VHDL[1] have recently become very popular to design the logical circuits all over the world. We, the Electronic Industries Association of Japan (EIAJ), have been working for the standardization activities with the Design Automation Sub-Committee (DASC) in IEEE. In the meanwhile, the VHDL and other related standards have evolved and improved. As the number of designers using VHDL increases so does the need to support the local language though designers have asked EDA tool vendors to enhance their products to support local language, it have often been rejected unfortunately.
    [Show full text]
  • IBM Enhanced 5250 Emulation Program User's Guide Version 2.4 Publication No
    G570-2221-05 IBM Enhanced 5250 Emulation Program User's Guide Version 2.4 GS70-2221-0S IBM Enhanced 5250 Emulation Program User's Guide Version 2.4 Note! ------------------~--------------------------------. Before using this information and the product it supports, be sure to read the general information under "Notices" on page xv. Sixth Edition (April 1994) This edition applies to the IBM Enhanced 5250 Emulation Program Version 2.4 and to all subsequent releases and modifications until otherwise indicated in new editions. The following paragraph does not apply to the United Kingdom or any country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This publication could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. Products are not stocked at the address below. Additional copies of this publication may be purchased from an IBM Authorized Dealer, IBM PC Direct™ (1-800-IBM-2YOU), IBM AS/400® Direct (1-800-IBM-CALL), or the IBM Software Manufacturing Company (1-800-879-2755). When calling, reference Order Number G570-2221 and Part Number 82G7303. Requests for technical information about these products should be made to your IBM Authorized Dealer or your IBM Marketing Representative.
    [Show full text]
  • Character Sets Reference Manual for Line Matrix Printers
    R Character Sets Reference Manual for Line Matrix Printers Character Sets Reference Manual for Line Matrix Printers R P/N 164308–001, Rev B Printronix, Inc. makes no representations or warranties of any kind regarding this material, including, but not limited to, implied warranties of merchantability and fitness for a particular purpose. Printronix, Inc. shall not be held responsible for errors contained herein or any omissions from this material or for any damages, whether direct, indirect, incidental or consequential, in connection with the furnishing, distribution, performance or use of this material. The information in this manual is subject to change without notice. This document contains proprietary information protected by copyright. No part of this document may be reproduced, copied, translated or incorporated in any other material in any form or by any means, whether manual, graphic, electronic, mechanical or otherwise, without the prior written consent of Printronix, Inc. All rights reserved. TRADEMARK ACKNOWLEDGMENTS Printronix, LinePrinter Plus, PGL and IGP are registered trademarks of Printronix, Inc. DEC is a registered trademark of Digital Equipment Corporation. Epson is a registered trademark of Seiko Epson. IBM is a registered trademark of Internation Business Machines Corporation. Proprinter is a registered trademark of IBM. Scalable type outlines are licensed from Agfa Corporation. Agfa is a registered trademark of Agfa Division, Miles Incorporated (Agfa). CG, Garth Graphic, Intellifont, and Type Director are registered trademarks of Agfa Corporation, and Shannon and CG Triumvirate are trademarks of Agfa Corporation. CG Bodoni, CG Century Schoolbook, CG Goudy Old Style, CG Melliza, Microstyle, CG Omega, and CG Palacio are products of Agfa Corporation.
    [Show full text]
  • Page 1 of 55 Overview of Installing SQL Server 2000 7/27/2007 File://C
    Overview of Installing SQL Server 2000 Page 1 of 55 Overview of Installing SQL Server 2000 Microsoft® SQL Server™ 2000 Setup creates a new installation of SQL Server 2000 or upgrades an earlier version. Before installing or upgrading to SQL Server 2000 it is recommended that you review the following topics. Topic Description Preparing to Install SQL Server 2000 Lists steps to take before running SQL Server 2000 Setup SQL Server 2000: Editions and Components Presents an overview of the editions of SQL Server 2000, installation options, and components Upgrading an Existing Installation of SQL Server Outlines options for upgrading to SQL Server 2000 from an earlier version For more information, see related topics in the table below. To install See SQL Server 2000 (typical installation of the relational database engine, How to install SQL Server 2000 (Setup) client tools, and client connectivity components) SQL Server 2000 client tools only How to install client tools only (Setup) (includes management tools and client connectivity components, no server required) SQL Server 2000 connectivity only How to install connectivity only (Setup) (installs only the client connectivity components, no other options) A named instance or multiple instances of SQL Server 2000 How to install a named instance of SQL Server 2000 (Setup) A SQL Server 2000 virtual server for failover clustering Before Installing Failover Clustering Analysis Services Installing Analysis Services English Query Installing English Query Preparing to Install SQL Server 2000 Before installing Microsoft® SQL Server™ 2000, consider the following: Be sure the computer meets the system requirements for Microsoft SQL Server 2000. For more information, see Hardware and Software Requirements for Installing SQL Server 2000 .
    [Show full text]
  • Rocket Universe NLS Guide
    Rocket UniVerse NLS User Guide Version 12.1.1 June 2019 UNV-1211-NLS-1 Notices Edition Publication date: June 2019 Book number: UNV-1211-NLS-1 Product version: Version 12.1.1 Copyright © Rocket Software, Inc. or its affiliates 1985–2019. All Rights Reserved. Trademarks Rocket is a registered trademark of Rocket Software, Inc. For a list of Rocket registered trademarks go to: www.rocketsoftware.com/about/legal. All other products or services mentioned in this document may be covered by the trademarks, service marks, or product names of their respective owners. Examples This information might contain examples of data and reports. The examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. License agreement This software and the associated documentation are proprietary and confidential to Rocket Software, Inc. or its affiliates, are furnished under license, and may be used and copied only in accordance with the terms of such license. Note: This product may contain encryption technology. Many countries prohibit or restrict the use, import, or export of encryption technologies, and current use, import, and export regulations should be followed when exporting this product. 2 Corporate information Rocket Software, Inc. develops enterprise infrastructure products in four key areas: storage, networks, and compliance; database servers and tools; business information and analytics; and application development, integration, and modernization. Website: www.rocketsoftware.com Rocket Global Headquarters 77 4th Avenue, Suite 100 Waltham, MA 02451-1468 USA To contact Rocket Software by telephone for any reason, including obtaining pre-sales information and technical support, use one of the following telephone numbers.
    [Show full text]
  • Making the FTC : an Approach to Material Connections Disclosures In
    Fordham Intellectual Property, Media and Entertainment Law Journal Volume 28 XXVIII Number 3 Article 3 2018 Making the FTC ☺: An Approach to Material Connections Disclosures in the Emoji Age Christina Sauerborn Fordham University School of Law, [email protected] Follow this and additional works at: https://ir.lawnet.fordham.edu/iplj Part of the Intellectual Property Law Commons Recommended Citation Christina Sauerborn, Making the FTC ☺: An Approach to Material Connections Disclosures in the Emoji Age, 28 Fordham Intell. Prop. Media & Ent. L.J. 571 (2018). Available at: https://ir.lawnet.fordham.edu/iplj/vol28/iss3/3 This Note is brought to you for free and open access by FLASH: The Fordham Law Archive of Scholarship and History. It has been accepted for inclusion in Fordham Intellectual Property, Media and Entertainment Law Journal by an authorized editor of FLASH: The Fordham Law Archive of Scholarship and History. For more information, please contact [email protected]. Making the FTC ☺: An Approach to Material Connections Disclosures in the Emoji Age Cover Page Footnote Online Editor, Fordham Intellectual Property, Media & Entertainment Law Journal, Volume XXVIII; J.D. Candidate, Fordham University School of Law, 2018; B.A., Individualized Study, with a concentration in Art and Business, New York University, 2011. The Author would like to thank Professor Olivier Sylvain for his guidance and feedback in developing this Note, and the IPLJ Editorial Board and staff for their hard work throughout the editorial process, especially E. Alex Kirk, Matt Hershkowitz, and Jillian Roffer. The Author would also like to thank her family and friends, especially Kathryn and Gary Sauerborn, James DiStefano, and Jessica Drake, for their unconditional love and support.
    [Show full text]