[prev in list] [next in list] [prev in thread] [next in thread] 

List:       linux-audio-dev
Subject:    Re: [LAD] Inter thread Communication: Design Approach
From:       Harry van Haaren <harryhaaren () gmail ! com>
Date:       2011-08-20 16:17:36
Message-ID: CAKudYbNWoVVLqMc-YhZ50Djg-pNP5vRH5G61oqNGabBQJfwMFA () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On Sat, Aug 20, 2011 at 4:04 PM, Gabriel Beddingfield <gabrbedd@gmail.com>wrote:

> IMHO, You're more or less going in the right direction.  There's two main
> ways to structure your EventType.. and they are both essentially using
> inheritance.  We'll call them "The C way" and "The C++ Way".  They are more
> or less equivalent.
>

Thanks for that! I like the C++ way, it seems more in line with my way of
doing things...
I spose I just gotta go derive some classes now :)

Cheers, -Harry

[Attachment #5 (text/html)]

<div class="gmail_quote">On Sat, Aug 20, 2011 at 4:04 PM, Gabriel Beddingfield <span \
dir="ltr">&lt;<a href="mailto:gabrbedd@gmail.com">gabrbedd@gmail.com</a>&gt;</span> \
wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; \
border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">

IMHO, You&#39;re more or less going in the right direction.  There&#39;s two main \
ways to structure your EventType.. and they are both essentially using inheritance.  \
We&#39;ll call them &quot;The C way&quot; and &quot;The C++ Way&quot;.  They are more \
or less equivalent.<br> </blockquote><div><br>Thanks for that! I like the C++ way, it \
seems more in line with my way of doing things...<br>I spose I just gotta go derive \
some classes now :)<br><br>Cheers, -Harry<br></div></div>



_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/listinfo/linux-audio-dev


[prev in list] [next in list] [prev in thread] [next in thread]