@hackage eventloop0.8.2.1

A different take on an IO system. Based on Amanda's IO loop, this eventloop takes a function that maps input events to output events. It can easily be extended by modules that represent IO devices or join multiple modules together. Each module exists of a initialize and teardown function that are both called once at startup and shutting down. During run-time, a module can provice a preprocessor function (which transforms input events before they get to the eventloop), and a postprocessor function (which transforms output events after they are received from the eventloop but before they are send off). Next to these bookkeeping functions, a module can exist of a (check for events and an event retrieve) function pair which result in input events and an addition to the event sender function which handles output events. This results in the following states: |Start|: initialize -> |Run-Time| -> teardown |Run-Time|: eventCheckers - Yes > preprocessors -> eventloop -> postprocessors -> event sender -> |Run-Time| |- No > |Run-Time| Each module has a piece of "memory"state which is defined by the module itself and all of the module states are combined in the IO state. When writinginstalling a module, modifications has to be made at certain points in the code due to the poor modularity of Haskell.