Re: ALSA API as standards

[Lennart Poettering <mznyfn@0pointer.de>]

On Fri, 23.11.07 15:54, Takashi Iwai (tiwai@suse.de) wrote:

Just a few random comments:

> /* I/O */
> 
> snd_input_stdio_open
> snd_input_stdio_attach
> snd_input_buffer_open
> snd_input_close
> snd_input_scanf
> snd_input_gets
> snd_input_getc
> snd_input_ungetc
> 
> snd_output_stdio_open
> snd_output_stdio_attach
> snd_output_buffer_open
> snd_output_buffer_string
> snd_output_close
> snd_output_printf
> snd_output_vprintf
> snd_output_puts
> snd_output_putc
> snd_output_flush

May I ask why these are exported at all? The seem to be some kind of
STDOUT/STDIN abstraction, and have no place in a sound API I would
say. Especially not in any "standardized" version of it.

> snd_config
[...]
> snd_config_iterator_entry

Same here, why does parsing config files of ALSA need to be part of
the audio API? I see no need for this.

> snd_pcm_dump
> snd_pcm_dump_hw_setup
> snd_pcm_dump_sw_setup
> snd_pcm_dump_setup
> snd_pcm_hw_params_dump
> snd_pcm_sw_params_dump
> snd_pcm_status_dump

And these? They are not even documented, or am I blind?

Lennart

-- 
Lennart Poettering                        Red Hat, Inc.
lennart [at] poettering [dot] net         ICQ# 11060553
http://0pointer.net/lennart/           GnuPG 0x1A015CC4