Cpp runtime naming conventions

[Rüdiger Franke]

Consider

package A
  package B
    model M
    end M;
  end B;
  package C
    model M
    end M;
  end C;
end A;

translateModel(A.B.M) with +simCodeTarget=Cpp generates files that have A.B.M in their names. The classes inside the files just contain M in their name. This exhibits the risk that A.B.M and A.C.M collide if they shall be linked together, e.g. in a hierarchical FMU.

Is this a bug or a feature?

One might alternatively use underscores instead of dots for class names, like A_B_M. The Cpp FMU code generation currently messes up models with dots in their names. This ticket needs to be clarified, in order to know in which direction to proceed.

[Rüdiger Franke]

SVN r25207 fixes the FMI Cpp export to consistently using short model identifiers, like M. This makes it work with the Cpp runtime.

Shouldn't the Cpp runtime be changed to using long model identifiers though, like A_B_M?

Basically some calls to

lastIdentOfPath(modelInfo.name) or identOfPath(modelInfo.name)

need to be replaced with

System.stringReplace(dotPath(modelInfo.name), ".", "_")

Or should identOfPath be used and let it return long model identifiers?

[Martin Sjölund]

Moved to new milestone 1.9.4

[Martin Sjölund]

Milestone pushed to 1.9.5

[Martin Sjölund]

Milestone renamed

[Martin Sjölund]

Ticket retargeted after milestone closed

[Martin Sjölund]

Milestone moved to 1.12.0 due to 1.11.0 already being released.

[Francesco Casella]

The milestone of this ticket has been reassigned to "Future".

If you think the issue is still valid and relevant for you, please select milestone 1.13.0 for back-end, code generation and run-time issues, or 2.0.0 for front-end issues.

If you are aware that the problem is no longer present, please select the milestone corresponding to the version of OMC you used to check that, and set the status to "worksforme".

In both cases, a short informative comment would be welcome.