Steve Harris wrote:
> To my mind it's better for us to develop a large suite of tools and
> plugins to demonstrate the viability and advantages before we go
I think we indeed need lots of testing tools - like debugging
hosts/plugins spiked with lots of pre/postcondition checks, or even some
validity checking libraries that could be easily inserted (#ifdef'ed)
into "real" hosts/plugins, to check plugin/host behaviour in "real world".
I recall what incomplete/buggy standard implementations did in Buzz and
VST worlds, and it'd be nice to have some tools to prevent repeating the
same nightmare.
As for "who will write it", I guess it can't be a single-person project,
because just one person is unlikely to come up with *all* the useful
checks (and it would be incredibly boring anyway).
Krzysztof
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@email-addr-hidden
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
Received on Wed Jan 23 16:15:02 2008
This archive was generated by hypermail 2.1.8 : Wed Jan 23 2008 - 16:15:02 EET