Attention is currently required from: jolly, pespin, fixeria.

Patch set 2:Code-Review +1

View Change

1 comment:

• File msc/BSC_ConnectionHandler.ttcn:

  • Patch Set #2, Line 68: inout charstring, CallParameters, ASCI_Event;

    imho this makes general handlig of Coord port more difficult, since one needs to check for different […]

    I would go the other way around: Why are there strings at all, and not more specific types going through the port? And regarding handling other messages: A simple default altstep that ignores all unsupported messages could be used to make old code backwards-compatible.

    TTCN-3 is a strongly typed language. Sending strings between two parts of our own code looks like it was python or some kind of weakly typed language. There are all the usual problems associated with strings like making a typo on one end would only be discovered at runtime instead of compile time, ...

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