“Interrupt” operator is actually “timeout”
Reported by Douglas Creager | April 27th, 2008 @ 07:33 PM | in 1.0-α2
The operator that's currently called “interrupt” (▵ ) is actually the timeout operator (▹).
The differences between the two are subtle. In P▹Q, it's an internal decision for P to timeout, and for the overall process to start behaving like Q. This is the semantics that we've implemented.
In P▵Q, on the other hand, it's an external decision. P's events and Q's events are both offered, and if any Q event is taken, P becomes deactivated.
We should change the code so that the operator that we've implemented has the right name.
Comments and changes to this ticket
-
Douglas Creager April 27th, 2008 @ 07:39 PM
- State changed from “new” to “resolved”
(from [58e5a3a4444fde5983b86b446359223f2ca9d598]) Current “interrupt” operator is actually “timeout”
The operator that's currently called “interrupt” is actually the CSP
“timeout” operator. All of the semantics are correct; it's just the
name of the operator that's wrong. This patch corrects this, in the
code, test cases, and all documentation.
Lighthouse: [#4 state:resolved]
-
Douglas Creager April 28th, 2008 @ 01:47 PM
- Milestone set to “1.0-α2”
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile »
An open-source refinement checker for the CSP process algebra.
People watching this ticket
Douglas Creager
Tags
Referenced by
-
5
Need to implement “interrupt” operator
This is related to ticket #4 — since what we actually im...