Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E EMADL2CPP
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • monticore
  • EmbeddedMontiArcEmbeddedMontiArc
  • generators
  • EMADL2CPP
  • Issues
  • #26
Closed
Open
Issue created Mar 14, 2021 by Andreas Wahlen@cracksalad

Output ports can not be used for further connects

When using an output port as a source of a connect statement, there will be no error or warning but no corresponding code will be generated.

This should either throw an error or just work. Could be helpful in situations like the following:

package ...;
component Test {
  port 
    in x,
    out y,
    out z;

  instance InstX instX;
  instance InstY instY;

  connect x -> instX.param;
  connect instX.res -> y;
  connect y -> instY.param; // this is the problematic line, one could of course also use instX.res again
  connect instY.res -> z;
}
Assignee
Assign to
Time tracking