diff options
| author | Raimo Niskanen <[email protected]> | 2016-10-20 22:28:10 +0200 |
|---|---|---|
| committer | Raimo Niskanen <[email protected]> | 2016-10-26 10:13:25 +0200 |
| commit | 0b4deedf278273205c9dcd2ed5d0b4b4d4d8fb9d (patch) | |
| tree | 59927c90348fbe4d9ea294cb00112aff14193f8e /lib/stdlib/doc/src/gb_trees.xml | |
| parent | f3f2b83e873592bcec47431a787c7cfffdd60685 (diff) | |
| download | otp-0b4deedf278273205c9dcd2ed5d0b4b4d4d8fb9d.tar.gz otp-0b4deedf278273205c9dcd2ed5d0b4b4d4d8fb9d.tar.bz2 otp-0b4deedf278273205c9dcd2ed5d0b4b4d4d8fb9d.zip | |
Rework timeout handling
Handling of timers and timeouts has been cleaned up
and generalized.
Semantic change regarding state timeout zero:
Previously if one state caused a state timeout zero and
managed to stay in the same state to insert additional
timeout zero(s) in the next state callback invocation, then
there would be only one timeout zero event. The mindset
was that the machine was faster then the timeout zero.
This has changed with the mindset that all state callback
invocations should be independent, so now the machine will
get one state timeout zero event per started state timeout
zero.
Note that just using zero timeouts is fairly esoteric...
Diffstat (limited to 'lib/stdlib/doc/src/gb_trees.xml')
0 files changed, 0 insertions, 0 deletions