Purpose

The C++ Support Package User's Manual is part of the documentation set that describes pSOSystem, the modular, high-performance real-time operating system environment from Integrated Systems, Inc.

This manual is intended to supplement the standard pSOSystem manual set, documenting the C++ specific support services provided. These services include the pSOSystem C++ Classes (library) and support for the C++ runtime.

This manual is intended primarily for pSOSystem embedded application developers who want to implement C++ applications.

Organization

This manual does not provide tutorial information about C++, nor is it meant to be a guide to creating new C++ applications.

This manual is organized as follows:

Chapter 1, ``Introduction,'' describes how to install the C++ support features into an existing C pSOSystem directory structure and discusses the changes to this directory tree. Also included is information on building C++ applications.

Chapter 2, ``C++ Interface Concepts,'' introduces the design goals, basic concepts, and implementation of the pSOSystem C++ Class Library. Compiler run-time support issues and the pSOSystem C++ implementation are also discussed.

Chapter 3, ``C++ Interface References,'' provides detailed reference descriptions (man pages) for the pSOSystem C++ interface.

Appendix A, ``pSOS+ C to C++ System Call Cross Reference,'' provides a cross reference listing of pSOSystem C++ functions and C system calls.

Appendix B, ``Building C++ Applications Using the pRISM Tool Set,'' provides information on building your C++ application using the pRISM tool set.

Appendix C, ``Building C++ Applications Using the Microtec Research Tool Set,'' provides information on building your C++ application using the Microtec Research (MRI) tool set.

Appendix D, ``Building C++ Applications Using MetaWare Compiler,'' provides information on building your C++ application using the MetaWare High C/C++ compiler.

Notation Conventions

The following notation conventions are used in this manual:

• Function names (q_receive), filenames (pdefs.h), keywords (int), and operators (!) that must be typed exactly as shown are presented in bold.
• Italics indicate that a user-defined value or name (drive:pathname) can be substituted for the italicized word(s) shown. Italics also indicate emphasis, such as when important terms are introduced.
• Keynames [Enter] are shown within square brackets. Keynames separated by hyphens are typed together. For example, to type [Ctrl-Shift-e], hold down the [Ctrl] and [Shift] keys and type the letter e.
• Example output is shown in constant width.

When using this manual, you might want to have on hand these other manuals that make up the basic documentation set:

• pSOSystem Installation Guide provides installation instructions for workstation and PC hosts.
• pSOSystem Getting Started contains an introduction to the pSOSystem environment, some tutorials, a description of board-support packages, configuration instructions, information on files and directories, and some board-specific information. It also includes introductory material on using the pROBE+ debugger.
• pSOSystem System Concepts contains detailed descriptions of the pSOS+ real-time kernel, the pSOS+m multiprocessing kernel, network programming, the pHILE+ file system manager, the pREPC+ ANSI C library, and the input/output system.
• pSOSystem Programmer's Reference contains detailed descriptions of all pSOSystem system services, interfaces and drivers, configuration tables, and memory usage.
• pSOSystem System Calls provides a reference of pSOS+, pHILE+, pREPC+, pNA+, and pRPC+ system calls and error codes.

Based on your software configuration, you may need to refer to the following manual:

• pROBE+ User's Guide describes how to use the pROBE+ system-level analyzer for monitoring pSOSystem execution.

To contact Integrated Systems Technical Support, call 1-800-458-7677, 1-408-980-1500 ext.501, or send a Fax to 1-408-980-1647.

You may also email problems to psos_support@isi.com, making sure to include the following information:

• Customer name, account number, and company name
• Customer identification number and project name
• Fax number and E-mail address
• Product(s), version, host, target, and cpu information
• A complete description of the behavior
• Commands or code sequence that will reproduce the problem

We actively seek suggestions and comments about our software and documentation, and anything else on your mind. You can mail your comments to ideas@isi.com.