It is sad that event based code is so hard to read.
I wish some programming language would let the programmer write the code as-if polling, but then transform the program automatically to something event based at compiletime.
Eg.
While(true):
if (button_is_pressed) do_x()
If (something_else) do_y()
The Linux select() API is nearly that, although it's rather cumbersome.
With the second I have to potentially worry about thread safety. What if while i’m busy doing X in response to a button press something else happens and I also need to do Y?
With the first version of the code it is pretty obvious what will happen (i will finish doing X and then I will do Y). With the second code I have to read my platform’s documentation to know if it will buffer the second event while the first is handled, or drop it, or call the handler from a different thread.
That's a pretty fundamental thing to understand about the platform you're using, isn't it? You learn it once, and then you never have to learn it again.
Plus, it's not entirely clear in your example what happens if "something else" occurs, and then while `do_y()` is being executed, a button press occurs. Is the button press event buffered, or is it dropped?
Also, given that you're proposing automatic transformation of programs (by the compiler?), and your `while` loop would become shorthand for some unspecified other program, there would potentially be a lot of hidden magic to be aware of. Your program could even be transformed into a program which would process the events in multiple threads.
I wish some programming language would let the programmer write the code as-if polling, but then transform the program automatically to something event based at compiletime.
Eg.
The Linux select() API is nearly that, although it's rather cumbersome.