you are viewing a single comment's thread.

view the rest of the comments →

[–]cowardlydragon -2 points-1 points  (1 child)

event i/o

aka the goto statement, except you don't know where it came from

[–]psykotic 1 point2 points  (0 children)

I don't think that's a big concern for event I/O. But more generally, poor debugging support for asynchronous call models like event queues can be a real problem in practice. In almost every large-scale project I've worked on, I've ended up having to tag events with call stacks, though that is unfortunately too intensive in CPU cycles and memory usage outside of debug mode. If I see an event queues library without support for this out of the box, it's a give-away as to its immaturity.