From: Chuckles <chuckleberryfinn@gmail.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Alsa Mixer api documentation.
Date: Mon, 25 Jul 2005 13:33:17 +0200 [thread overview]
Message-ID: <29d8345905072504337b900491@mail.gmail.com> (raw)
In-Reply-To: <1122254407.31270.1.camel@mindpipe>
So that's a no then. I had been looking at the source for amixer.c but
what can I tell ya? Pouring over 1500 lines of uncommented, (mostly)
static methods written in C is hardly the best way to learn an api now
is it? (Do linux developers hate c++/oo programming or do they just
willfully ignore it?) Apart from the opening few lines about the gnu
gpl there are 3 (count 'em) 3, one line comments in a source file of
over 1500 lines. But if the alsa developers can't be bothered to write
the docs I suppose I don't have much choice.
Cathal
On 7/25/05, Lee Revell <rlrevell@joe-job.com> wrote:
> On Mon, 2005-07-25 at 01:46 +0200, Chuckles wrote:
> > So...is there? If anyone can even give me a simple "open mixer, set
> > pcm to 50%, close mixer" example that'd be great.
>
> Why don't you look at the source to xmms or mplayer?
>
> Lee
>
>
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id\x16492&op=click
next prev parent reply other threads:[~2005-07-25 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-24 23:46 Alsa Mixer api documentation Chuckles
2005-07-25 1:20 ` Lee Revell
2005-07-25 11:33 ` Chuckles [this message]
2005-07-25 13:11 ` Jaroslav Kysela
2005-07-25 14:20 ` Alsa Mixer api documentation. (Damn u C programmers!) Chuckles
2005-07-26 13:12 ` Jaroslav Kysela
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29d8345905072504337b900491@mail.gmail.com \
--to=chuckleberryfinn@gmail.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=rlrevell@joe-job.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.