Oracle C++ Call Interface Programmer's Guide

OTT Utility Reference
Once the OTT utility has read the name of a database entity, it translates the name
from the character set used by the OTT utility to the compiler's character set. If a
translation of the name appears in the INTYPE file, then the OTT utility uses that
translation.
Otherwise, the OTT utility attempts to translate the name as follows:
1. If the OTT character set is a multibyte character set, all multibyte characters in
the name that have single-byte equivalents are converted to those single-byte
equivalents.
2. The name is converted from the OTT character set to the compiler character set.
The compiler character set is a single-byte character set such as US7ASCII.
3. The case of letters is set according to how the CASE parameter is defined, and
any character that is not legal in a C or C++ identifier, or that has no translation
in the compiler character set, is replaced by an underscore character (_). If at
least one character is replaced by an underscore, then the OTT utility gives a
warning message. If all the characters in a name are replaced by underscores,
the OTT utility gives an error message.
Character-by-character name translation does not alter underscores, digits, or
single-byte letters that appear in the compiler character set, so legal C or C++
identifiers are not altered.
Name translation may, for example, translate accented single-byte characters such
as o with an umlaut or an a with an accent grave to o or a, with no accent, and may
translate a multibyte letter to its single-byte equivalent. Name translation will
typically fail if the name contains multibyte characters that lack single-byte
equivalents. In this case, the user must specify name translations in the INTYPE file.
The OTT utility will not detect a naming clash caused by two or more database
identifiers being mapped to the same C name, nor will it detect a naming problem
where a database identifier is mapped to a C keyword.
Restriction Affecting the OTT Utility: File Name Comparison
Currently, the OTT utility determines if two files are the same by comparing the
filenames provided by the user either on the command line or in the INTYPE file.
But one potential problem can occur when the OTT utility needs to know if two
filenames refer to the same file. For example, if the OTT-generated file foo.h requires
a type declaration written to foo1.h, and another type declaration written to
/private/smith/foo1.h, then the OTT utility should generate one #include if
the two files are the same, and two #includes if the files are different. In practice,
How to Use the Object Type Translator Utility 7-135