Programmer's Guide to the Pro*C/C++ Precompiler Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index



Go to previous file in sequence Go to next file in sequence

System-Specific References


This appendix groups together in one place all references in this guide to system-specific information.


System-Specific Information

Each of the sections below describes briefly a reference in this guide to system-specific Pro*C behavior. System-specific information is described in the appropriate Oracle system-specific documentation for your platform.

Location of Standard Header Files

The location of the standard Pro*C header files--sqlca.h, oraca.h, and sqlda.h--is system specific. On UNIX systems, they are located in the $ORACLE_HOME/sqllib/public directory. For other operating systems, see your Oracle system-specific documentation.

Specifying Location of Included Files for the C Compiler

When you use the Pro*C command-line option INCLUDE= to specify the location of a non-standard file to be included, you should also specify the same location for the C compiler. The way you do this is system specific. See pages 3 - 8 and 3 - 9.

ANSI C Support

Some C compilers support the ANSI C standard; some do not. Make sure to use the CODE= option to make the C code that Pro*C generates compatible with your system's C compiler. See page 3 - 12.

Struct Component Alignment

C compilers vary in the way they align struct components, usually depending on the system hardware. Use the sqlvcp() function to determine the padding added to the .arr component of a VARCHAR struct. See the section ``Finding the Length of a VARCHAR Array Component'' [*]. See also page 3 - 59.

External Datatypes

Some Oracle external datatypes are designed to support host datatypes in languages other than C. For example, DECIMAL and DISPLAY are used mainly for PL/I and COBOL. See the section ``External Datatypes'' [*].

Size of an Integer

The size in bytes of integer datatypes is system dependent. See the section ``Integer'' [*].

Size of ROWID

The binary external size of a ROWID datatype is system dependent. See the section ``ROWID'' [*].

Byte Ordering

The order of bytes in a word is platform dependent. See the section ``Unsigned'' [*].

Connecting to Oracle

Connecting to Oracle using the SQL*Net V1 or V2 drivers involves system-specific network protocols. See the section ``Connecting to Oracle'' [*] for more details.

Linking in an XA Library

You link in your XA library in a system-dependent way. See the section ``Linking'' [*], and your Oracle installation or user's guides, for more information.

Location of the Pro*C Executable

The location of the Pro*C Precompiler is system specific. See the section ``Precompiler Command'' [*], and your installation or user's guides, for more information.

System Configuration File

Each precompiler installation has a system configuration file. This file is not shipped with the precompiler; it must be created by the system administrator. The location (directory path) which Pro*C searches for the system configuration file is system dependent. See the section ``Configuration Files'' [*] for more information.

INCLUDE Option Syntax

The syntax for the value of the INCLUDE command-line option is system specific. See the ``INCLUDE'' section [*].

Compiling and Linking

Compiling and linking your Pro*C output to get an executable application is always system dependent. See the section ``Compiling and Linking'' [*], and the following sections, for additional information.

User Exits

Compiling and linking Oracle Forms user exits is system specific. See Chapter 13.




Go to previous file in sequence Go to next file in sequence
Prev Next
Oracle
Copyright © 1997 Oracle Corporation.
All Rights Reserved.
Go to Product Documentation Library
Library
Go to books for this product
Product
Go to Contents for this book
Contents
Go to Index
Index