Lars Luthman <[EMAIL PROTECTED]> writes: > On Thu, 2007-11-29 at 14:55 +0200, Nedko Arnaudov wrote: >> Lars Luthman <[EMAIL PROTECTED]> writes: >> >> > On Thu, 2007-11-29 at 05:59 +0200, Nedko Arnaudov wrote: >> >> Also, i doubt we need three "count" members in Event_Port_Buffer >> >> structure. used_size - number of used events is perfectly fine by >> >> itself. I dont see why plugin should know whether buffer is actually >> >> larger. >> > >> > It needs to know that for an output buffer. >> >> Well, port is either input or output, why not use same variable/member >> (with appropriate naming)? > > You could, but there isn't really much to gain from it. The host will > want to keep track of the buffer capacity in some way so those 4 bytes > have to go somewhere, and I think having the same variable mean > different things for input and output buffers makes things more > confusing.
And supplying things to plugins that they should not (and do not) care about is not confusing? And we assume that plugins would be more than hosts after all... -- Nedko Arnaudov <GnuPG KeyID: DE1716B0>
pgplEKZU6XxN8.pgp
Description: PGP signature
_______________________________________________ Linux-audio-dev mailing list [email protected] http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev
