On Tue, 29 Jan 2002, Roger E Critchlow Jr wrote:
> Paul Davis writes:
> > >Hello all,
> > >
> > > it seems that I've finished an initial version of documentation
> > >for alsa-lib's configuration files and PCM interface. Here is URL:
> >
> > looks like a decent start. i hope i can find time to improve some
> > parts of this. in reading the section on the syntax of config files,
> > however, i find myself overwhelmed by the question "why another small
> > language?" it seems really hard to explain to myself, let alone anyone
> > else. its possible that some introductory material may help here, but
> > i'm not sure. it seems *really* odd that alsa-lib has its own
> > configuration language when there are so many other options. the
> > existence of this language isn't so clear when you've just been
> > hacking .asoundrc files, but seeing it defined like this makes me much
> > more uneasy about it all. rather strange reaction, i suspect.
> >
> > not that i'm really suggesting we do much about it. i think.
> >
>
> Ah, but it's not "another small language", it's the same language that
> X11 and java resource files use, with two extensions that are well
> chosen:
> 1) a compound node syntax so that you don't need to type the
> entire a.b.c.d.etc... path name for each resource.
> 2) an array node syntax that generates the 0, 1, 2, ... leaf names
> for you.
>
> At least, that's my reading.
>
> Now, how do I get libasound to give me the root of the snd_config_t
> that it's using by default, so I can see how it's put together?
The pointer to global configuration is 'snd_config' variable, but you
should call snd_config_update() before to make sure that the configuration
is loaded.
Jaroslav
-----
Jaroslav Kysela <[EMAIL PROTECTED]>
SuSE Linux http://www.suse.com
ALSA Project http://www.alsa-project.org
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
