Initializers in C++ generation

[robiwan]

I've tried to add constructor initializers for attributes by filling in the "Initial" field, but EA doesn't seem to generate them?

Also, how do I set initial values for superclasses that don't have default constructors? I can't add them in the code since EA deletes them on code generation.

If I add the initializers, then reverse engineer I thought EA might "pick them up", but again regenerating the code removes all initializers...

Help?
/R

[Eve]

Have a look at http://www.sparxsystems.com/EAUserGuide/index.html?cpp_conventions.htm.

A search in this forum also gives http://www.sparxsystems.com.au/cgi-bin/yabb/YaBB.pl?board=general;action=display;num=1160867243 which provides some template modifications to do a bit more.

[pborcic]

I can live with EA not generating the constructor initializers for attributes, but does it have to erase the contents of the Initial field when you synchronize the model?
Is this a bug? Because it is very annoying.  

[robiwan]

Actually if you use the "initializer" tagged value for the class, you can have roundtrip engineering. To "automatically" fill in this value, you can write your initializers in the C++ code and then synchronize the model. I agree that this is not as nice as having the Initial field of the attributes being generated as code, but it is ok.

[pborcic]

I already use the "initializer" tag for calling base class constructors which works well.
My real complaint is that it wipes out whatever is in the attribute Initial field even though code generation doesn't use it. I just need to use it for documentation purposes for now (it keeps the guys in QA happy   ).
Though it would be nice if it did work, especially for static constants. I wouldn't think it was that difficult. Even Rational Rose can do it (or at least it used to).  

[krhohio]

I think that the situation with this in 2021 is the same as it was in 2007?