[LAD] Conciderations of Design

harryhaaren at gmail.com harryhaaren at gmail.com
Fri Nov 11 22:19:44 UTC 2011

Hi All,

Recent thoughts of mine include changing the "direction" of operations in  
real-time program design:
Eg: Don't call a set() on a Filter class to tell it its cutoff, every time  
there's a change,
but make it ask a State class what its cutoff should be every time it runs.

I'm now considering implementing this pattern, but I'm wondering have  
others done this before?

Along the same lines, say I have a single linked list of AudioElements, and  
the 3rd element needs info, should
it request it, be told it, or have some other system to inform it of events?

I'm seeing downsides to each approach:
1: Tell it on every change -> performance hit
2: Request it every time it runs -> Keeping control over the many values &  
unique ID's of class instances

Experience & Opinions all welcomed, -Harry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20111111/7305db02/attachment.html>

More information about the Linux-audio-dev mailing list