draft proposal 2

I must take the middle path in this fine argument regarding how much OO should be.
First, C++ virtuals are the same as keeping a function pointer, only it's value is set at "new" time (please lets not start a pointless argument on that point), so regarding this point Aitor is absolutly right and performance is hardly effected by OO (for as long as it is done smartly, which I sure will be the case here).
The problem with "fine grained OO" is optimization flexability and readability, what if I developed a function that Transforms and Quantizes at the same time, then we practically loose two great classes (and at least 8 files ;) . The smallest data parts like blocks are best kept as plain structs and arrays which can be allocated and handled sequencially  (and in assembly as well) with smart memory access and will allow much room for optimizations.
Take a look at the list of classes I suggested, I think that the usage of such grained OO will give us the necessary both OO && (plain)C flexability for much more optimizations in all aspects (CPU/Memory/Algorithmic) and will keep the code small clean well organized and readable for those who are less experinced in OO and more in plain DSP coding kinda stuff.

-----------------------------------------------------------------------
Walla! Mail, Get Your Private, Free E-mail from Walla! at:
http://mail.walla.co.il