Event-driven flows -- Andrzej Krzemieński
This post is in response to two claims about coroutines: 1) Their reference function parameters may become dangling too easily, and 2) They are indistinguishable from regular functions from the declaration alone.
Event-driven flows
by Andrzej Krzemieński
From the article:
A canonical example of an event-driven flow is the handling of signals in C. Signals will be risen at unpredictable points in time, so rather than actively checking for them, we define a callback and associate it with the indicated signal:
signal(SIGINT, on_interrupt);After having performed this association, we move on to doing other things. It is the implementation (system, or parts of the program we do not write) that will make sure to invoke the callback when the signal is risen (if at all). We can illustrate it with a diagram:
xplore how the C++ standard evolved across versions with interactive side-by-side diffs
aster Language Engine, Unique Constexpr Debugger, DAP Support, and Much More
