Skip to content
Snippets Groups Projects
Commit e60910de authored by benjamin.franksen's avatar benjamin.franksen
Browse files

seq: removed an out-dated comment

The first removed paragraph was just wrong. The second one proposed
alternatives which I no longer regard as being superior. Connection loss
is not supposed to happen regularly during normal operation, so the
small overhead of waking all state sets is negligable in practice.
parent 72c4e7d8
No related branches found
No related tags found
No related merge requests found
......@@ -494,16 +494,6 @@ void seq_conn_handler(int connected, void *arg)
Why each one? Because pvConnectCount and pvMonitorCount should
act like monitored anonymous channels. Any state set might be
using these functions inside a when-condition and it is expected
that such conditions get checked whenever these counts change.
Another reason is the pvConnected built-in: a state set with a
when(pvConnected(var)) should be able to make progress
if the channel is now connected.
TODO: This is really a crude solution. It would be better to post
special events reserved for pvConnectCount and pvMonitorCount
(if we could assume safe mode is always on we'd just turn them
into anonymous PVs), and to post the regular PV event for the
variable that has connected (or disconnected). */
that such conditions get checked whenever these counts change. */
ss_wakeup(sp, 0);
}
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment