Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E Eclipse eTrice
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 43
    • Issues 43
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Eclipse Projects
  • Eclipse eTrice™
  • Eclipse eTrice
  • Issues
  • #41

Closed
Open
Created Apr 28, 2022 by Eyrak Paen-Rochlitz@epaenDeveloper

Name collisions between room classes in different namespaces when linking

extern functions/structs of room classes are not qualified by room model namespace which leads to collisions when linking

Example (actor classes with the same name in different namespaces cause linking error due to duplicate function and struct definitions):

RoomModel m1 {
    SubSystem subsys {
        ActorRef inst1: m1.a
        ActorRef inst2: m2.a
    }

    ActorClass a {
    }
}

RoomModel m2 {
    ActorClass a {
    }
}
Assignee
Assign to
Time tracking

Copyright © Eclipse Foundation, Inc. All Rights Reserved.     Privacy Policy | Terms of Use | Copyright Agent