Bouml reference manual - Fedora Project Packages GIT repositories

file:///C:/uml/BOUML/bouml_3.0/doc/TOUT.html204 of 378 07/10/2007 15:55When you push the button default declaration, the form specified through the generation settings is proposed, this last may be modifiedas you want, even to produce illegal source code.When you do not want to generate the C++ header file (for instance for the main), empties the declaration manually or using the buttonnot generated in C++.${NAME} produce the artifact name capitalized, ${Name} produce the artifact name with the first letter capitalized, at least ${name}produce the artifact name without modification.${comment} is replaced by the artifact description adding //${description} is replaced by the artifact description without adding //${includes} is replaced by the automatically generated #include and using forms (done by the C++ code generator, not made by the dialogwhich produce a fixed form). It is also a good place to add your #include and using forms, when the ones produced by the code generatorare not sufficient. The C++ code generator does not look at in the operations body, only the operation's profiles, relations and attribuclasses inheritances etc ... are used to compute the needed #include list. ${includes} and ${all_includes} are exclusive.${all_includes} is replaced by all the automatically generated #include and using forms, it is also a good place to add your #include andusingforms, when the ones produced by the code generator are not sufficient. In this case the code generator doesn't produce declarations in theheader file nor #include in the source file, except the ones added by you. ${all_includes} and ${includes} are exclusive.${declarations}is replaced by the class declarations generated automatically (done by the C++ code generator, not made by the dialog which producefixed form). It is also a good place to add your declarations, when the ones produced by the code generator are not sufficient.${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.${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.The forms @{property}are replaced by the value of the corresponding user property if it is defined for the class or at an upper level, else it is not substituted.Artifact dialog, tab C++ sourceThis tab is only available for the source artifacts and allows to give the definition of the C++ source file generated for the artifact, it ivisible only if C++ is set through the menu LanguagesWhen you push the button default declaration, the form specified through the generation settings is proposed, this last may be modifiedas you want, even to produce illegal source code.