Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > IDL Code > Mapping information > Summary of Mappings for IDL code (IDL code) > Value type mapping for IDL (IDL code)
  
Value type mapping for IDL (IDL code)
For each Value Type, ACS generates a valuetype declaration in the appropriate IDL file. ACS generates code similar to this:
// Type declarations
valuetype Value_Type1
{
...
};
ACS uses Value Types for generating the content of a Deployment Plan's Component Deployment Plan (CDP) file.
The generation of a Value Type in an IDL file is derived from the items it owns and properties of the Value Type.
You can generate a boxed valuetype declaration that includes a type through a Type Definition that is stereotyped by the «CORBABoxedValue» stereotype. Tell me more...
Child items:
If the Value Type owns Attributes, ACS generates attribute declarations. For Attribute mapping information, see Attribute mapping for IDL.
If the Value Type owns Operations, ACS generates a function declaration. For Operation mapping information, see Operation mapping for IDL.
Properties:
If the Description property has a value, ACS generates the Description as a comment on the line before the valuetype declaration.
ACS generates the Name property as the name of the valuetype.
Note ACS may modify the valuetype name that is added to the code to make it valid for IDL. You can specify the exact valuetype name to add to the code through the CODE_GENERATION_NAME property of a Value Type.
Other properties are ignored.
Tag Definitions:
The «CORBAValue» stereotype applies the following Tag Definitions.
If the tagged value of the isCustom tag definition is set to TRUE, ACS generates the value type declaration using the custom keyword.
If the tagged value of the is Truncatable tag definition is set to TRUE, ACS generates the value type declaration using the truncatable keyword.