On Sun, Feb 17, 2013 at 4:45 PM, Harry van Haaren wrote:
The only reason you need this is because you memcpy the object.
You're effectively serializing your object and passing them over the
ringbuffer. If you do it this way, you should at least consider
explicitly embedding the type and length as the first member of
EventBase (and have each derived class set their own type and length
in their constructors), and reading those before touching the object
Linux-audio-dev mailing list