Abramo Bagnara wrote:
> No, I intend that generally only engine pass data from producers to
> consumers.
>
> However a producer may ask data to other producer (generally not visible
> to engine). Same for consumer.
>
> All is engine driven: i.e. audio is obtained from producer first, then
> elaborated and passed to consumers one unit at a time.

Okay, I understand this now - the engine can call the producers and
consumers in the correct order to make sure everything works out.

> All documentation is up-to-date and embedded in source.
> You can generate it using:
> doxygen doxygen.cfg
> in alsa-lib/doc directory (the generated documentation goes in
> alsa-lib/doc/doxygen/html)

Well, I couldn't find a doxygen.cfg file in either the
alsa-lib-0.9.0beta3 nor alsa-lib-0.5.10b tarball, and my improvised
doxygen.cfg did not work very well.

However, even looking directly at the source I can't find any docs.
The code looks neat and tidy, but no docs.  To be sure I wrote a
script to strip out all the comments from all the source files.  I
read all these and I'm not any wiser.

Am I stupid, or did you just send me on a wild goose chase ?  Is this
a joke ?  I'm meant to use the source, am I ?  Why didn't you say ?

Jim

-- 
 Jim Peters         /             __   |  \              Aguazul
                   /   /| /| )| /| / )||   \
 jim@aguazul.      \  (_|(_|(_|(_| )(_|I   /        www.aguazul.
  demon.co.uk       \    ._)     _/       /          demon.co.uk

Reply via email to