Christian Menard

Should we close this issue then?

Also see the discussion in #398. Implementing this should make it easy to implement testing for diagrams (#802).

I learned that the interpretation of the contents within `{=...=}` also happens in other places. For instance, the C code generator interprets `{=foo*=}` as a token type. edit: see #1479...

Is this issue addressed by #620?

I think there are two issues at place here. The first is that we sometimes interpret contents of `{=...=}` which we shouldn't do. This is what this issue is about....

#544 is purely syntactical. It would help in eliminating the `{=` and `=}` here but not solve the underlying issue. To solve the issue we would either need to interpret...

> The following data were generated using a script that I added in the a-b-test branch. This script is a work-in-progress, and I am not sure if it is something...

@petervdonovan I think most of your points could be done with the python script, but require a bit of work. Some of your points, have also annoyed me in the...

I transferred this to the LF repo, because this needs to be solved at the level of the code generator.

The multi ports and reactors as they work now are more a case study and not a fully thought through design. In particular, there are checks missing in the validator...