diff options
author | Raimo Niskanen <[email protected]> | 2016-02-29 11:36:27 +0100 |
---|---|---|
committer | Raimo Niskanen <[email protected]> | 2016-02-29 11:36:27 +0100 |
commit | e660572b020da58c89149c7f052c7127cc0263cb (patch) | |
tree | b4d3c27ec17605a06f7e0b72e05248957b7bebe7 /bootstrap | |
parent | c2b8e6cdbc884e93cabe78e9fc9dcc040eb828eb (diff) | |
download | otp-e660572b020da58c89149c7f052c7127cc0263cb.tar.gz otp-e660572b020da58c89149c7f052c7127cc0263cb.tar.bz2 otp-e660572b020da58c89149c7f052c7127cc0263cb.zip |
Remove the remove_event action and all alike
Removing events from the internal queues is not necessary with
the choosen semantics of the event queue vs. hibernate.
In an early implementation it was possible by combining
hibernate with e.g. postpone to get an event in the queue
that you would not see before processing the postponed event,
and therefore should you decide to cancel a timer it was
essential to be able to remove that unseen event from the queue.
With the choosen semantics you will have to postpone or generate
an event for it to be in the event queue, and if you e.g. postpone
a timeout event and then cancel the timer it is your mistake.
You have seen the event and should know better than to try to
cancel the timer.
So, the actions: remove_event, cancel_timer, demonitor and unlink
are now removed.
There have also been some cleanup of the timer handling code.
Diffstat (limited to 'bootstrap')
0 files changed, 0 insertions, 0 deletions