MIME-version: 1.0 Content-type: text/plain; charset="ISO-8859-1" Content-transfer-encoding: 8bit Summing up?? (1) compiles to (2) ,runs into (2) "Executed STOP process" (3) compiles to (Appendix),runs into (4) "All IF branches failed" (5) compiles to (Appendix),runs into (6) "Executed STOP process" (7) compiles to much, runs into (8) "Terminating application" Q1. And you are saying they are ALL the same ?-) Q2. What's the purpose of saying that they are formally the same if they aren't practically the same? Q3. How will KRoC behave? You don't have to answer this, as an engineer I pretty much _feel_ the answer. And besides, all "runs into" are just fine with me, they all stop me one way or the other! PS. I know you haven't been even mentioning (5), but I formally uncorrectly assumed that's what Peter first meant:-) (1) STOP (2) SETERR(MSG_STOP); (3) IF FALSE SKIP (4) SETERR(MSG_IF); (5) IF TRUE STOP (6) SETERR(MSG_STOP); (7) CHAN OF INT a, b: PAR SEQ a ! 42 b ! 99 INT x, y: SEQ b ? x a ? y (8) SETERR (MSG_TA); "Terminating application" (SPOC) "Erroneous channel usage" (Peter/Denis) -------------------------------- APPENDIX: #C // IF FALSE SKIP IF FALSE SKIP SPOC COMPILES TO: // IF FALSE SKIP if (false) { } else { SETERR(MSG_IF); } ------------------------------ #C // IF TRUE STOP IF TRUE STOP SPOC COMPILES TO: // IF TRUE STOP if (true) { SETERR(MSG_STOP); } else { SETERR(MSG_IF); } -------------------------------- Cheers, Oyvind Teig, Autronica, Trondheim, Norway Oyvind.Teig@autronica.no Tel.: +47 73 58 12 68 Fax.: +47 73 91 93 20 My name starts with "Oslash": Øyvind