DOCSLIB.ORG

Tools and Utilities Guide

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Tools and Utilities Guide 3.1 TOOLS AND UTILITIES GUIDE • ERROR MESSAGES • WINSIGHT'" • MAKE • HELP/RESOURCE COMPILERS • TLiNK BORLAND Borlanct c++ Version 3.1 Tools and Utilities Guide BORLAND INTERNATIONAL INC. 1800 GREEN HILLS ROAD P.O. BOX 660001, scons VALLEY, CA 95067-0001 Copyright © 1991, 1992 by Borland International. All rights reserved. All Borland products are trademarks or registered trademarks of Borland International, Inc. Other brand and product names are trademarks or registered trademarks of their respective holders. Windows, as used in this manual, refers to Microsoft's implementation of a windows system. PRINTED IN THE USA. Rl 10 9 8 7 6 5 4 c o N T E N T s Introduction 1 Examples ....................... 24 Automatic dependency checking ... 25 Chapter 1 Import library tools 3 Implicit rules . .. 25 IMPDEF: The module definitions Macros' ........................... 28 manager ............................. 3 Defining macros ................. 29 Classes in a DLL .................... 4 U sing macros. .. 29 Functions in a DLL . .. 5 Using environment variables as IMPLIB: The import librarian ........... 6 macros ......................... 29 Re-creating IMPORT. LIB ............. 7 Substitution within macros ........ 30 IMPLIBW: The import librarian for Special considerations ............ 30 Windows ............................ 7 Predefined macros ............... 30 Select an import library .............. 7 Defined Test Macro ($d) ........ 31 From a DLL ...................... 7 File name macros ................ 32 From a module definition file ....... 7 Base file name macro ($*) ....... 32 Creating the import library . .. 8 Full file name macro ($<) . .. 32 Chapter 2 Make: The program File name path macro ($:) ....... 33 manager 9 File name and extension macro How MAKE works . .. 10 ($.) . .. 33 Starting MAKE ...................... 10 File name only macro ($&) ...... 33 Command-line options ............. 11 Full target name with path macro The BUlL TINS.MAK file ............ 13 ($@) .......................... 33 A simple use of MAKE ............... 13 All dependents macro ($**) . .. 34 Crea ting makefiles ................... 16 All out of date dependents macro Components of a makefile . .. 16 ($?) .......................... 34 Comments ........................ 17 Macro modifiers ................. 34 Command lists for implicit and explicit Directives . .. 35 rules ............................. 17 Dot directives ..................... 36 Prefixes ........................ 18 .precious ........................ 36 Command body and operators ..... 18 .path.ext ........................ 36 Compatibility option .......... 19 .suffixes ........................ 37 Batching programs .............. 20 File-inclusion directive ............. 38 Executing commands ............ 21 Conditional execution directives ..... 38 Explicit rules ..................... 22 Expressions allowed in conditional Special considerations ........... 23 directives ....................... 40 Multiple explicit rules for a single Error directive . .. 41 target ........................... 24 Macro undefinition directive ........ 42 The compatibility option -N . .. 42 /0 (overlays) ..................... 68 IP (pack code segments) ........... 69 Chapter 3 TLlB: The Turbo librarian 45 It (tiny model.COM file) .......... 69 Why use object module libraries? ...... 46 lTd and ITw (target options) ...... 70 The TLIB command line .............. 46 I v (debugging information) ........ 70 The operation list .................. 47 lye (expanded memory) ........... 71 , File and module names ........... 48 I yx (extended memory) ........... 71 TLIB operations. .. 48 The module definition file ............ 72 U sing response files ................... 49 Module definition file defaults ...... 72 Creating an extended dictionary: The IE A quick example .................. 73 option .............................. 49 Module definition reference .......... 74 Setting the page size: The IP option .... 50 CODE ........................... 74 Advanced operation: The IC option. ,... 50 DATA ........................... 75 Examples ........................... 51 DESCRIPTION ................ ,... 76 Chapter 4 TLlNK: The T~Jrbo linker 53 EXETYPE ........................ 76 Invoking TLINK .. .. 53 EXPORTS ........................ 76 An example of linking for DOS ...... 54 HEAPSIZE ....................... 77 An example of linking for Windows .. 55 IMPORTS ........................ 78 File names on the TLINK command LIBRARy ........................ 78 line .............................. 55 NAME .......................... 79 Using response files ................ 56 SEGMENTS ...................... 79 The TLINK configuration file ........ 57 STACKSIZE ...................... 80 Using TLINK with Borland C++ STUB ............................ 80 modules ......................... 58 Chapter 5 USing WinSight 83 Startup code .................... 59 Getting started ..................... 83 Libraries ....................... 59 Getting out ....................... 84 BGI graphics library .......... : . 60 Choosing a view .................... 84 Ma th libraries ................ 60 Picking a pane .................... 84 Run-time libraries ............. 61 Arranging the panes ............... 85 Using TLINK with BCC ............ 62 Getting more detail ............... 85 TLINK options ..................... 62 Class detail .................... 85 The TLINK configuration file ....... 62 Window detail .................. 85 (32-bit code) ................... 13 63 Using the window tree .............. 85 A (align segments) ............... I 63 Pruning the tree .................. 86 (case sensitivity) ............. ~ .. Ic 63 Showing child windows ......... 86 ./C (case sensitive exports) ......... 64 Hiding child windows ........... 86 I d (duplicate symbols) ............ 64 Finding a window ................ 86 I e (no extended dictionary) ........ 65 Leaving Find Window mode ..... 86 (uninitialized trailing segments) .. Ii 65 Spying on windows ............... 87 (line numbers) .................. II 65 Working with classes ................ 87 IL (library search paths) ........... 65 U sing the Class List pane .......... 87 1m, Is, and Ix (map options) ....... 66 Spying on classes ................. 87 (ignore default libraries) ........ In 68 Taking time out ..................... 88 Turning off tracing . .. 88 Layout of the Help text .......... 110 Suspending screen updates .......... 88 Type fonts and sizes . .. 111 Choosing messages to trace ........... 88 Graphic images ................... 112 Filtering out messages .............. 89 Creating the Help topic files .......... 113 Message tracing options ............ 89 Choosing an authoring tool ........ 113 Formatting message parameters ... 89 Structuring Help topic files . .. 113 Logging traced messages .......... 89 Coding Help topic files ............ 114 WinSight windows . .. 93 Assigning build tags ............ 115 Class List pane ............. "....... 93 Assigning context strings ........ 116 Display format .................. 93 Assigning titles ................ 117 Window Tree pane . .. 94 Assigning keywords ............ 118 Display format .................. 94 Creating multiple keyword Message Trace pane ................ 94 tables ........................ 119 Format ......................... 95 Assigning browse sequence numbers . .. 120 Chapter 6 RC: The Windows resource Organizing browse sequences .. 120 compiler 97 Coding browse sequences . .. 122 Creating resources ................... 97 Creating cross-references between Adding resources fo an executable ..... 98 topics ......................... 122 Resource compiling from the IDE .... 98 Defining terms ................. 123 Resource compiling from the command Creating definition topics ...... 123 line .. "............................ 99 Coding definitions ............ 124 Resource compiling from a makefile .. 99 Inserting graphic images . .. 124 Resource Compiler syntax. .. 99 Creating and capturing bitmaps .. 124 Chapter 7 HC: The Windows Help Placing bitmaps using a graphical compiler 101 word processor.................. 125 Creating a Help system: The development Placing bitmaps by reference ..... 125 cycle .............................. 101 Managing topic files . .. 126 How Help appears to the user ...... 102 Keeping track of files and topics .. 127 How Help appears to the help writer. 103 Creating a help tracker .......... 127 How Help appears to the help Building the Help file . .. 129 programmer ..................... 104 Creating the Help project file ....... 129 Planning the Help system ............ 104 Specifying topic files .............. 130 Developing a plan ................ 104 Specifying build tags .............. 131 Defining the audience ........... 104 Specifying options ................ 131 Planning the contents ............ 105 Specifying error reporting . .. 132 Planning the structure ........... 106 Specifying build topics .......... 132 Displaying context-sensitive Help Specifying the root directory ..... 133 topics ......................... 107 Specifying the index . .. 134 Determining the topic file structure .. 108 Assigning a title to the Help Choosing a file structure for your system ........................ 134 application . .. 108 Converting fonts . .. 134 Designing Help topics ............. 110 Changing font sizes ............. 135 Multiple keyword tables ......... 136 iii Compressing the file ............ 136 Canceling Help ................. 148 Specifying alternate context strings .. 137
Load more

Recommended publications
  • Embrace and Extend Approach (Red Hat, Novell)
    Integrated Development Environments (IDEs) Technology Strategy Chad Heaton Alice Park Charles Zedlewski Table of Contents Market Segmentation.............................................................................................................. 4 When Does the IDE Market Tip? ........................................................................................... 6 Microsoft & IDEs ................................................................................................................... 7 Where is MSFT vulnerable?................................................................................................. 11 Eclipse & Making Money in Open Source........................................................................... 12 Eclipse and the Free Rider Problem ..................................................................................... 20 Making Money in an Eclipse World?................................................................................... 14 Eclipse vs. Microsoft: Handicapping the Current IDE Environment ................................... 16 Requirements for Eclipse success......................................................................................... 18 2 Overview of the Integrated Development Environment (IDE) Market An Integrated Development Environment (IDE) is a programming environment typically consisting of a code editor, a compiler, a debugger, and a graphical user interface (GUI) builder. The IDE may be a standalone application or may be included as part of one or more existing
    [Show full text]
  • VERSION 2.0 Referene MANUAL
    VERSION 2.0 REFERENe MANUAL BORlAnD INTERNATIONAL Borland International 4113 Scotts Valley Drive Scotts Valley, California 95066 Copyright Notice© This software package and manual are copyrighted 1983, 1984 by BORLAND INTERNATIONAL Inc. All rights reserved worldwide. No part of this publication may be reproduced, transmitted, transcribed, stored in any retrieval system, or translated into any language by any means without the express written per­ mission of BORLAND INTERNATIONAL Inc., 4113 Scotts Valley Drive, Scotts Valley, CA 95066, USA. Single CPU License The price paid for one copy of TURBO Pascal licenses you to use the product on one CPU when and only when you have signed and returned the License Agreement printed in this book. Disclaimer Borland International makes no warranties as to the contents of this manual and specifically disclaims any implied warranties of merchantability or fitness for any particular purpose. Borland International further reserves the right to make changes to the specifications of the program and contents of the manual without obligation to notify any person or organization of such changes. Fifth edition, October 1984 Printed in the United States of America 98765 TABLE OF CONTENTS INTRODUCTION ............................................. 1 The Pascal Language .........................................1 TURBO Pascal ..............................................1 Structure of This Manual ..................................... 2 Typography ............................................... 3 Syntax Descriptions
    [Show full text]
  • Adapting MSP to Microsoft C++ ©James T. Smith, 1999 1. Introduction A. General Comments I. Purpose
    Adapting MSP to Microsoft C++ ©James T. Smith, 1999 1. Introduction a. General comments i. Purpose (1) MSP was developed in a PC environment with the original version of Borland C++, then adapted in several stages to Version 5.0, the standard for this book. Many readers, however, prefer to or must use a different compiler. The environment most frequently mentioned that is somewhat close to the book’s is Microsoft’s. This file describes my adaptation of MSP as a suite of Microsoft Visual C++ Win32 Console Applications. (2) It’s an adaptation guide, not a completed product. Most MSP features described in this book work under the adaptation, but it has not been used for further development. With it, you can see how these features work in your Microsoft environment. To use it for a major project, however, you’ll probably want to select only the appropriate MSP modules. You’ll need to test the adaptation much more thoroughly, and probably add minor cor- rections as needed by your specific application. ii. Major differences (1) Microsoft’s complex mathematics module is implemented with templates. That adds more levels of implicit conversions for the compiler to consider when resolving overloaded function declarations. Many more ambiguities would result, and some methods MSP uses to resolve them would no longer work. This would cause so many changes that you’d lose sight of the rest. So the adaptation contains a completely rewritten complex module. (2) Microsoft handles hardware faults, such as overflow detected by the floating-point processor, by throwing“structured exceptions”.
    [Show full text]
  • AIM104-Software Library
    2192-09193-000-000 AIM104-Software Library Software A Utility Disk is supplied with your AIM104. It contains a host of software utilities designed specifically for each AIM104. Please refer to the README.TXT file on the disk for further information. It also includes a test program EXAMP-01.EXE which may be used to confirm access to the board. Introduction Arcom Control Systems produces a complete range of high quality Input/Output (I/O) cards for the PC104 bus. In order to support these I/O cards as fully as possible a complimentary set of high quality software support products is also available. This software library forms part of the software support. This software support has been developed to support Borland C++ versions 3.1 and 4.52, running on 386 CPUs, Pentium CPUs and Arcom Target boards, in both DOS and Windows operating systems. It is presented to the user in the form of standard static library files. This library can then be incorporated into custom application code giving the user all the software facilities needed to use all the hardware features included on an Arcom PC104 I/O card. This manual contains the basic details of what is contained within this library. For a more detailed description please read the Word 2.0 file genman.doc contained in the DOCS sub-directory of the installation disk or in the DOCS sub-directory of the directory you install to. The list below shows the boards supported within the scope of this library. All commonly used modules are listed, however those that fall outside this list are not supported within this software library.
    [Show full text]
  • Lotus V. Borland: Defining the Limits of Software Copyright Protection Jason A
    Santa Clara High Technology Law Journal Volume 12 | Issue 1 Article 7 January 1996 Lotus v. Borland: Defining the Limits of Software Copyright Protection Jason A. Whong Andrew T. S. Lee Follow this and additional works at: http://digitalcommons.law.scu.edu/chtlj Part of the Law Commons Recommended Citation Jason A. Whong and Andrew T. S. Lee, Lotus v. Borland: Defining the Limits of Software Copyright Protection, 12 Santa Clara High Tech. L.J. 207 (1996). Available at: http://digitalcommons.law.scu.edu/chtlj/vol12/iss1/7 This Case Note is brought to you for free and open access by the Journals at Santa Clara Law Digital Commons. It has been accepted for inclusion in Santa Clara High Technology Law Journal by an authorized administrator of Santa Clara Law Digital Commons. For more information, please contact [email protected]. CASENOTE LOTUS V. BORLAND: DEFINING THE LIMITS OF SOFTWARE COPYRIGHT PROTECTION Lotus Development Corporationv. BorlandInternational, Inc., 49 F.3d 807 (1st Cir. 1995)* Jason A. Whongt and Andrew T.S. Leet TABLE OF CONTENTS INTRODUCTION .............................................. 207 BACKGROUND .............................................. 209 D ISCUSSION ................................................ 211 A. Method of Operation ................................ 211 B. Computer Associates International,Inc. v. Altai, Inc... 215 CONCLUSION ................................................ 216 "[E]verything ... has been done already ... who are we to improve upon them? We can only attempt, respectfally, to repeat."' INTRODUCTION On January 16, 1996, only eight days after hearing oral argu- ments in the case, an equally divided2 Supreme Court let stand the First Circuit's decision in Lotus Development Corp. v. Borland Inter- * Copyright @ 1995 Jason A. Whong and Andrew T.S.
    [Show full text]
  • Appendix 1 the Borland Pascal Package
    Section 1. Installation 555 Appendix 1 The Borland Pascal Package Section 1. Installation When you open your carton of Borland Pascal, you may be frightened by the tens of kilos of books and mountain of disks. This Appendix will get you started on installation and use of the system to write your Pascal programs. Even if you have already installed Borland Pascal and are using it, you may find some useful tips here, so please thumb through these pages. (There is much useful information in the Borland Pascal User's Guide, which is in your package.) For starters, your computer should have a goodly chunk of free disk space in one hard disk partition. If you install the complete Borland Pascal system, that will take about 30M. The programs with this book will fill about 2M, and when you start writing programs, who knows? Before you start installation, decide which partition to use, and note how much free disk space is available. Don't push a partition to its absolute limit. Start the "Install" program by inserting Disk 1 into the A: drive and typing A:INSTALL <Enter> (By the time this book appears you will probably be able to acquire BP on CD­ ROM and install it that way.) The "Install" program gives you lots of options, and explains what it is doing as it runs. If you have adequate disk space, the easiest course is to install everything. If you want to install only what you need for using this book, when the "Install" program prompts you for what to install/omit, you can omit the Windows version, the Assembler, the Profiler, the Debugger, the Turbo Vision package, and the On-line compilers.
    [Show full text]
  • 1 in the UNITED STATES DISTRICT COURT for the EASTERN DISTRICT of TEXAS TEXARKANA DIVISION DISC LINK CORPORATION, Plaintiff, V
    Case 5:06-cv-00295-DF-CMC Document 255 Filed 07/23/07 Page 1 of 10 IN THE UNITED STATES DISTRICT COURT FOR THE EASTERN DISTRICT OF TEXAS TEXARKANA DIVISION DISC LINK CORPORATION, ' ' Plaintiff, ' ' ' v. ' CIVIL ACTION NO. 5:06cv00295 ' H&R BLOCK DIGITAL TAX SOLUTIONS, ' JURY TRIAL DEMANDED LLC F/K/A H&R BLOCK DIGITAL TAX ' SOLUTIONS, INC., BLOCK FINANCIAL ' CORPORATION and RIVERDEEP INC., A ' LIMITED LIABILITY COMPANY, ' ' Defendants. ' ' CONSOLIDATED WITH: ' DISC LINK CORPORATION, ' ' Plaintiff, ' CIVIL ACTION NO. 5:07-CV-58 ' v. ' ' ORACLE CORPORATION, SAP ' AMERICA, INC. d/b/a SAP AMERICAS, ' SAP AG, BENTLEY SYSTEMS, INC., ' ' SPSS, INC., SOLIDWORKS ' CORPORATION, CMS PRODUCTS, INC., ' SONIC SOLUTIONS, COREL ' CORPORATION, COREL, INC., MISYS ' INTERNATIONAL BANKING SYSTEMS, ' INC., ADTRAN, INC., EASTMAN KODAK ' COMPANY, CA, INC., UGS CORP., ' NUANCE COMMUNICATIONS, INC., ' KOFAX IMAGE PRODUCTS, INC., ' ' BUSINESS OBJECTS AMERICAS, ' BUSINESS OBJECTS SA, TREND MICRO ' INCORPORATED (CALIFORNIA ' CORPORATION), EMC CORPORATION, ' BORLAND SOFTWARE CORPORATION, ' NOVELL, INC., COMPUWARE ' CORPORATION and ' AVID TECHNOLOGY, INC., ' ' ' Defendants. ' 1 Case 5:06-cv-00295-DF-CMC Document 255 Filed 07/23/07 Page 2 of 10 FOURTH AMENDED COMPLAINT Plaintiff DISC LINK CORPORATION files this Fourth Amended Complaint against Defendants H&R BLOCK DIGITAL TAX SOLUTIONS, LLC, f/k/a H&R BLOCK DIGITAL TAX SOLUTIONS, INC., BLOCK FINANCIAL CORPORATION, RIVERDEEP INC., A LIMITED LIABILITY COMPANY, ORACLE CORPORATION, SAP AMERICA, INC. d/b/a SAP AMERICAS, SAP AG, BENTLEY SYSTEMS, INC., SPSS, INC., SOLIDWORKS CORPORATION, CMS PRODUCTS, INC., SONIC SOLUTIONS, COREL CORPORATION, COREL, INC., MISYS INTERNATIONAL BANKING SYSTEMS, INC., ADTRAN, INC., EASTMAN KODAK COMPANY, CA, INC., UGS CORP., NUANCE COMMUNICATIONS, INC., KOFAX IMAGE PRODUCTS, INC., BUSINESS OBJECTS AMERICAS, BUSINESS OBJECTS SA, TREND MICRO INCORPORATED (CALIFORNIA CORPORATION), EMC CORPORATION, BORLAND SOFTWARE CORPORATION, NOVELL, INC., COMPUWARE CORPORATION and AVID TECHNOLOGY, INC., alleging as follows: I.
    [Show full text]
  • Borland C++ Power Programming
    Borland C++ Power Programming Borland C++ Power Programming Clayton Walnum PROGRAMMING SERIES i SAMS/q3 Borland C++ Power Prog Paula 2-17-93 FM lp7 Borland C++ Power Programming Borland C++ Power Programming 1993 by Que Corporation All rights reserved. Printed in the United States of America. No part of this book may be used or reproduced in any form or by any means, or stored in a database or retrieval system, without prior written permission of the publisher except in the case of brief quotations embodied in critical articles and reviews. Making copies of any part of this book for any purpose other than your own personal use is a violation of United States copyright laws. For information, address Que Corporation, 11711 N. College Ave., Carmel, IN 46032. Library of Congress Catalog No.: 93-83382 ISBN: 1-56529-172-7 This book is sold as is, without warranty of any kind, either express or implied, respecting the contents of this book, including but not limited to implied warranties for the book’s quality, performance, merchantability, or fitness for any particular purpose. Neither Que Corporation nor its dealers or distributors shall be liable to the purchaser or any other person or entity with respect to any liability, loss, or damage caused or alleged to be caused directly or indirectly by this book. 96 95 94 93 8 7 6 5 4 3 2 1 Interpretation of the printing code: the rightmost double-digit number is the year of the book’s printing; the rightmost single-digit number, the number of the book’s printing.
    [Show full text]
  • Web Based C++ Compilers
    Session 2532 Web-based C++ Compiler Aleksander Malinowski, Bogdan M. Wilamowski Bradley University, Peoria, IL / University of Wyoming, Laramie, WY Abstract This paper reports the successful use of Web-based interface to C++ compilers. There are several benefits that make networked software desirable. A web-based application can be used remotely throughout any network connection. Any operating system can be used to access it, making it platform independent. There is no local installation or maintenance work necessary. Access can be controlled and limited if required by software license agreement. Internet Compilers Package (ICP) is an example of a networked software-engineering tool. Different compiler packages can be used for various stages of application development providing either maximum error detection or code optimization. Introduction During the process of software development frequently more than one compiler package is required. Some products are known to be very useful for locating errors or debugging, while others perform extremely well when a program or library is in the final stage of development and should be optimized as much as possible. Also when facing obscure error messages, which may result in a time-consuming search for the error, a different error message from the second compiler frequently cuts that time dramatically. Therefore students should be to some extend exposed to different compilers at some point in their software courses curriculum. Although all necessary software is installed in the computer laboratories, most students prefer to work on their computers at home or dormitory and connect to the university network. That situation creates unnecessary burden either for the network administrators who have to install additional software on many machines of non-standard configuration, or on students who must purchase and install on their own several software packages along their full course of study.
    [Show full text]
  • Delphi 7 for Windows Quick Start
    Quick Start Borland® Delphi ™ 7 for Windows™ Borland International, Inc., 100 Borland Way P.O. Box 660001, Scotts Valley, CA 95067-0001 www.borland.com Refer to the DEPLOY document located in the root directory of your Delphi 7 product for a complete list of files that you can distribute in accordance with the Delphi License Statement and Limited Warranty. Borland may have patents and/or pending patent applications covering subject matter in this document. The furnishing of this document does not give you any license to these patents. Please refer to the product CD or the About dialog box for the list of applicable patents. COPYRIGHT © 1983–2002 Borland Software Corporation. All rights reserved. All Borland brand and product names are trademarks or registered trademarks of Borland Software Corporation in the United States and other countries. All other marks are the property of their respective owners. Printed in the U.S.A. HDE1370WW21000 7E5R0802 0203040506-9 8 7654321 D3 Contents Chapter 1 Compiling and debugging projects . 3-6 Introduction 1-1 Deploying applications. 3-8 Internationalizing applications . 3-8 What is Delphi? . 1-1 Types of projects . 3-8 Registering Delphi . 1-2 CLX applications . 3-9 Finding information . 1-3 Web server applications . 3-9 Online Help . 1-4 Database applications. 3-10 F1 Help . 1-4 BDE Administrator . 3-11 Developer support services and Web site . 1-5 SQL Explorer (Database Explorer) . 3-11 Typographic conventions . 1-6 Database Desktop . 3-11 Chapter 2 Data Dictionary . 3-11 Custom components . 3-11 A tour of the environment 2-1 DLLs .
    [Show full text]
  • Table of Contents
    Atılım University Department of Computer Engineering Table of Contents 1. DESCRIPTION OF THE PROJECT...............................................................................................3 1.1. PROJECT OUTCOME .......................................................................................................................3 2. OBSERVED SOFTWARE FROM THE MARKET.......................................................................4 2.1. A TURKISH SOFTWARE: KIMKIM 2.0 FOR MS WINDOWS ..............................................................4 2.1.1. Screenshots of KimKim for Ms Windows ..............................................................................4 2.1.2. Other Features of KimKim....................................................................................................7 2.2. A FOREIGN SOFTWARE FROM “ADAM SYSTEMS”: TRAKMATE .....................................................8 2.2.1. Features of TrakMate............................................................................................................8 2.2.2. Screenshots of TrakMate for Windows................................................................................10 2.3. A TURKISH SOFTWARE: AMP CUSTOMER FOLLOW-UP 7.03 FOR WINDOWS ...............................14 2.3.1. What is it used for? .............................................................................................................14 2.3.2. Who may use this software?................................................................................................15
    [Show full text]
  • Using Borland C++ Tutorial (Last Update Aug 21, 1998 by R
    Using Borland C++ Tutorial (Last update Aug 21, 1998 by R. Tront) This tutorial provides an introduction to using Borland C++. Borland C++ comes with several compilers/linkers/ debuggers: some are for use from a (DOS) command line, and some are for use within a window-based Integrated Development Environment (IDE). The IDE provided is a single application that allows you to edit, project manage, compile, link, and debug your program files. This tutorial starts out with an explanation for first year computing students of command line environments and of writing programs targeted for running under a command line operating system like DOS. It then moves on to using the IDE to write command line programs that will run and can be debugged in a simple window, but it does not describe MS-Windows application programming. Along the way, it introduces proper programming of multi-module applications. Introduction The master operating system (OS) program of a computer is designed to accept operational commands of various types from users. In most operating systems, the user can interact with the OS via a simple command line interface. A command line interface uses simple text characters rather than bit-mapped graphics. The screen scrolls up as the user and computer write information to the bottom of the screen. The user is prompted on the left (often with just a “>”) to enter a command which (s)he must have memorized. The command often has parameters following it (usually not in brackets). A common command is to type the name of a program file, which the operating system takes as a request to start the application program contained in that program file.
    [Show full text]