Integrations (PTC products, 3rd party products and code) > Code integration (Ada, ARINC 653, C, C#, C++, IDL, Java, SQL and VB) > C++ code > Generating C++ code > Generating C++ code > Modeling C++ code in Modeler > Setting up interfaces for generating C++ code (C++ code)
  
Setting up interfaces for generating C++ code (C++ code)
In addition to the standard Interface properties in Modeler, you can apply the «C++ Class» stereotype to an Interface, and then use its Tag Definitions to define C++ specific information.
1. If you have not done so already, add the C++ Profile package to your Model. How?
2. Set the standard properties of the Interface as required. Tell me more...
3. If you want to generate a Model's or Package's Interfaces in a specific order, order the Interfaces as required. Tell me more...
4. Apply the «C++ Class» stereotype to the Interface.
For information about applying Stereotypes to an item, see Applying a Stereotype to a model item.
5. Open the Interface's Property Pages, and then click the C++ Class tab.
For information about setting the tagged value of a Tag Definition, see Setting a tagged value for an applied Tag Definition.
6. If you want to specify a header file comment, specify the text as the tagged value of the C++ Header File Comment tag definition.
7. If you want to specify header file #includes to files not modeled in Modeler, specify the #includes text as the tagged value of the C++ Header Include tag definition.
* 
You model #includes to files modeled in Modeler through Dependencies.
8. If the Interface is scoped to a Class and you want to specify that the Interface is a non-member, that is, the Interface is not a member of the owning Class but you want it to appear in the owning Class' Header file, set the tagged value of the C++ Non Member tag definition to TRUE.
9. If you want the Interface to be generated inline when used as a type, set the tagged value of the C++ Anonymous Item tag definition to TRUE.
10. If you want to specify an inheritance list for the Interface, specify the text as the tagged value of the C++ Inheritance List tag definition.
11. If you want to specify friend classes and structs that are modeled in the Model, reference those Classes, Data Types and Interfaces through the C++ Friend tag definition. If you want to specify friend classes and structs that are not modeled in the Model, specify the text of the friend declarations as the tagged value of the C++ Friend Text tag definition.
12. If you want to specify forward declarations to classes, structs, unions or enums, reference those Classes, Data Types, Interfaces or Type Definitions through the C++ Forward Declarations tag definition. If you want to specify forward declarations to items not modeled in the Model, specify the text of the forward declarations as the tagged value of the C++ Forward Declaration Text.
13. If you want to specify the linkage, set the tagged value of the C++ Linkage tag definition as required, for example, extern "C".
14. If you want to specify using declarations and directives for the Interface, specify the text as the tagged values of the C++ Using Decls and C++ Using Directives tag definitions. Note that if the C++ Using Decls and C++ Using Directives tag definitions are both blank, ACS will generate a 'using namespace std' statement when necessary.
15. If the Interface owns a State Diagram through a State Machine and you do not want to generate state machine code to implement that State Diagram, set the tagged value of the C++ Generate State Machine tag definition to FALSE.