--20cf303a31b1fe205304b3ae5561
Content-Type: text/plain; charset=ISO-8859-1> - how should one handle memory management of the messages? Is it ok for
Oops, perhaps I missed the boat on the ringbuffer, is the whole point that
with a ring buffer the memory for the max number of messages is
pre-allocated and we can just call by value in and out of the ringbuffer
without any memory management?
thanks
Iain
--20cf303a31b1fe205304b3ae5561
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
- how s=
hould one handle memory management of the messages? Is it ok for Engine to =
allocate memory for new
messages and have them destroyed on receipt, - or should I =
have queue delete the memory and return by value when messages are fetched?=
- what is the crustimony proceedcake for allocated memory from an engi=
ne?Oops, perhaps I missed the boat o=
n the ringbuffer, is the whole point that with a ring buffer the memory for=
the max number of messages is pre-allocated and we can just call by value =
in and out of the ringbuffer without any memory management?
thanksIain
--20cf303a31b1fe205304b3ae5561--
LINUX® is a registered trademark of Linus Torvalds in the USA and other countries.
Linuxaudio.org logo copyright Thorsten Wilms © 2006.
Hosting provided by the Virginia Tech Department of Music and DISIS.