Bouml reference manual - Fedora Project Packages GIT repositories

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html310 of 378 07/10/2007 15:55containing the deployment view where the artifact is defined.${definition} is replaced by the definition of the classes associated to the artifact.${namespace_end} is replaced by the } forms, dependent on the namespace specifications associated to the package containing thedeployment view where the artifact is defined.@{xyz} is replaced by the user property value in case xyz is the key of this property. The property if searched first for the artifact, ifnot found for the deployment view containing the artifact, if not found in the package containing the deployment view etc ...artifact source C++The generated file name is the artifact's name with the extension specified in the first C++ tab of the generations settings.In BOUML the generated code is obtained by the substitution of macros in a text, the macros known by the C++ code generator are :${comment} is replaced by the description of the artifact adding //${description} is replaced by the artifact description without adding //${includes} if ${all_includes} is not used in the header definition, it is replaced by the automatically generated #include and usingforms, corresponding to the declaration generated in the header file. If ${all_includes} is used in the header definition, it is replacedby the #include of the header. It is also a good place to add your #include and using forms.${namespace_start} is replaced by the namespace xx { forms, dependent on the namespace specifications associated to the packagecontaining the deployment view where the artifact is defined.${members} is replaced by the non inline members of the classes associated to the artifact.${namespace_end} is replaced by the } forms, dependent on the namespace specifications associated to the package containing thedeployment view where the artifact is defined.@{xyz} is replaced by the user property value in case xyz is the key of this property. The property if searched first for the artifact, ifnot found for the deployment view containing the artifact, if not found in the package containing the deployment view etc ...ClassThe C++ definition of a class is set through the Uml, Parametrized, Instantiate and C++ tabs of the class dialog.A C++ type definition may be a class, a struct, an union, an enum or a typedef, depending on the stereotype and its translation in C++ (seegeneration settings).In BOUML the generated code is obtained by the substitution of macros in a text, the macros known by the C++ code generator are :${comment} is replaced by the description of the class adding //${description} is replaced by the class description without adding //${template} produce a template declaration in case the class is a template class${name} is replaced by the class's name${inherit} is replaced by the class inheritance${members} is replaced by the code generated for all the class's members (relations, attributes, operations and extra members)following the browser order.${items} only for the enums, is replaced by the enum's items@{xyz} is replaced by the user property value in case xyz is the key of this property. The property if searched first for the class, ifnot found for the container of the class (an other class of a class view) etc ...In the special case where the class is declared external, its C++ type declaration must contains at least one line indicating how the nameof the class is generated, the other lines will be added in the header file of the components referencing the class. By default the first lineonly contain ${name} meaning that the name is produced unchanged, the only allowed keywords are ${name}, ${Name} and ${NAME}.