Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > Ada Code > Generating Ada code > Mapping information for generation > Mapping information for Ada 83 generation scheme > Basic type mapping for generating Ada 83 (Ada code)
  
Basic type mapping for generating Ada 83 (Ada code)
The mapping of basic types is defined through the [Datatype Mappings] section of the Ada_Sync.ini file, which resides in the 'PTC Integrity Modeler\Modeler\System\AdaGen' folder. If you create a basic type in the Model, you may have to map it to an Ada type in the Ada_Sync.ini file:
If the Basic Type name does not contain spaces and its case is as you want it generated, you do not have to map the Basic Type to an Ada type.
If the Basic Type name needs to be generated as a different type, you must map the Basic Type to an Ada type. For example, short=integer.
If the Basic Type name contains spaces, you must map the Basic Type to an Ada type. You can map a Basic Type name to itself, for example, my type=my type. Failure to do so results in spaces being generated as underscores. If you then reverse engineer the code, the data type will be changed to an uninterpreted data type in the Model that contains underscores instead of spaces.
If the Basic Type name has the wrong case, you must map the Basic Type to an Ada type with the correct case specified. For example, My Type=my type.
Ada_Sync.ini is installed with the following data type mappings defined (the Basic Type name to the left of the equals sign is not case sensitive, the Ada name to the right of the equals sign is case sensitive):
any=UNDEFINED_TYPE
char=Character
Date=UNDEFINED_TYPE
double=Float
int=Integer
long=Integer
octet=UNDEFINED_TYPE
short=Integer
unsigned long=Natural
unsigned short=Natural
void=UNDEFINED_TYPE
If a data type is not defined, ACS uses the default specified in the [Datatype Default] section of the Ada_Sync.ini file.