Namespaces and C++ code generation

[clearwa]

I am attempting to generate C++ source from a class model.  I have a set of packages that looks like this:

Root
-Package1
--Package2
--Package3

I've set Package1 as a namespace root; I want the classes generated in packages 1&2 to be in their appropriate namespaces, ie. I'd expect to see code of the form

namespace Package2 {
...
};

I've set C++ options to generate namespaces.  I've had a look at the templates but I really don't want to fiddle around in that area.  Does anyone have some insight for me here?

Thanx in advance,
Allan Clearwaters

[Falconne]

I have the same problem. Anyone know how to solve this?

[Kevin G. Watson]

 [smiley=2vrolijk_08.gif] Hi ya

Eerm... what are you getting?

namespace-1 {
        namespace-2 {
                  .....
                             }
        }

?

Kevin

[Falconne]

No, I am getting nothing. I have created packages at various levels and set them as "Namespace Roots" but they don't get generated to namespace { ... } the class definitions just get generated without a namespace.

Even if I reverse engineer simple code with namespace definitions, they don't get resolved into packages (and regenerating code from that immediately afterwards just creates flat definitions without namespaces).

[Eve]

Packages set as namespace root are not generated as namespace.  In the example from the first post, Package1 should be a namespace root (it represents the root level namespace) and Package2 and Package3 should not (they need to be generated).

That sounds like what the first poster is doing, and it should work.  If you want to reverse engineer namespaces into packages you'll need to use import source directory.

[Falconne]

Thanks Simon. I misunderstood the documentation.

The namespaces topic was only talking about Java and it seemed to imply that a package had to be set as a namespace root for a "package" keyword to be added to the top of classes defined inside that package (I may have misunderstood that as well). I assumed it was the same theory for c++ namespaces.

[DanG83616]

The Select Property Type dialog is irritating me. My C++ namespace is

namespace Insitu
{
   namespace Component
   {
   };
};

My model for the component has Class Model and under that imported source for the component.

MyModel
- ComponentPackage <- version controlled
---Class Model <- marked as root to get the correctly generated code
-----Insitu
-------Component

Select Property Type dialog presents Class Model in the In Namespace pulldown. All of my components are structured as above. Thus, when working on a composition involving more than one component the In Namespace lets me select from n Class Model options. I'm glad they are all listed but I'd rather see Insitu.ComponentA, Insitu.ComponentB, etc. As it is I have to click and see. It's not horrible but could be nicer. Any suggestions?

thx