Attention is currently required from: pespin.

View Change

1 comment:

• File library/L1CTL_Types.ttcn:

  • Patch Set #1, Line 859: template L1ctlMessage

    Just adding those would have been far quicker

    Yes, but I would still want to understand how would this affect the validation/compilation/execution, rather than quickly (and blindly) doing what you suggested. My current understanding is that adding `(present)` to receive templates does not bring noticeable improvements. I am not convinced by your arguments, sorry.

    It's a discussion like adding "static" or "const" to a variable in C

    In the case of `static` or `const` in C, I do see the benefits of using those keywords. And many of us could provide enough examples how `static` and/or `const` improved readability or prevented them from shooting their own legs. But here it feels more like a theoretical improvement.

    Out of curiosity, I even compared the resulting C++ code with and without the `(present)` in the `tr_FooBar` definition: no changes, except the `module_checksum[]`. So I am assuming that TITAN implicitly defaults to `(present)`.

To view, visit change 36254. To unsubscribe, or for help writing mail filters, visit settings.