Opened 9 years ago
Last modified 7 years ago
#3600 closed defect
Hierarchical stream connectors are not handled correctly — at Version 1
| Reported by: | Francesco Casella | Owned by: | somebody |
|---|---|---|---|
| Priority: | high | Milestone: | 2.0.0 |
| Component: | Frontend | Version: | |
| Keywords: | Stream connectors | Cc: | alberto.leva@… |
Description (last modified by )
If a hierarchical connector contains N > 1 stream connectors, the compiler complains:
Invalid stream connector XXX: A stream connector must have exactly one flow variable, this connector has N flow variables.
This is incorrect: each individual connector has its own flow variable, and these should not be mixed up when generating the expressions for inStream() and actualStream() involving them.
In order to handle hierarchical stream connectors, one should not just flatten them out. Separate connection sets should be built for each individual stream connector in the hierarchical connector
The attached package demonstrates the problem
Change History (2)
by , 9 years ago
| Attachment: | TestConnector.mo added |
|---|
comment:1 by , 9 years ago
| Description: | modified (diff) |
|---|
Note:
See TracTickets
for help on using tickets.
Test package