[LAD] Inter thread Communication: Design Approach

[Paul Davis]

On Thu, Sep 1, 2011 at 2:37 PM, Fons Adriaensen <fons at linuxaudio.org> wrote:

> That's assuming that the event's virtual execute() has access to
> all it needs. In all cases I've encountered that is not the case:
> the event triggers something in the context where it is received
> and processing it requires access to that context's data.
> It's a problem for which I don't know a clean C++ solution.

depending on the exact type of thing you're talking about, isn't this
is place for closures, functors, etc. etc. ?