From: Florian Bomers <Florian.Bomers@sun.com>
To: ALSA devel <alsa-devel@lists.sourceforge.net>
Subject: use new API ?
Date: Wed, 06 Nov 2002 09:18:29 -0800 [thread overview]
Message-ID: <3DC94EE5.398AA22B@sun.com> (raw)
Sorry for re-posting, especially if the answer is already "in the queue".
I reformulate the question:
Is it more likely that
- the already changed function prototypes, which are usable by defining
ALSA_PCM_NEW_HW_PARAMS_API, change in future, or
- that the deprecated functions will be removed ?
I am talking here e.g. of snd_pcm_hw_params_get_period_size()
Are there any incompatibilities likely from 0.9.0rc5 to 0.9.0FCS ?
Thanks,
Florian
-------- Original Message --------
Subject: [Alsa-devel] save to use new API ?
Date: Mon, 04 Nov 2002 11:38:41 -0800
From: Florian Bomers <Florian.Bomers@Sun.COM>
Organization: Sun Microsystems, Inc.
To: ALSA devel <alsa-devel@lists.sourceforge.net>
Hi,
if I released a program now in binary form, is it safer to use the new function
prototypes of alsa-lib by defining ALSA_PCM_NEW_HW_PARAMS_API or better use the
old, deprecated ones ?
My program compiles with or without, and I'd prefer to use the new API, but I
noticed that when I compile against rc5, it doesn't even run with rc4, so I fear
that my binary compiled against rc5 won't run with later versions of ALSA lib.
Thanks for letting me know.
Florian
--
Florian Bomers
Java Sound
Java Software/Sun Microsystems, Inc.
http://java.sun.com/products/java-media/sound/
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Alsa-devel mailing list
Alsa-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-devel
-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
reply other threads:[~2002-11-06 17:18 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3DC94EE5.398AA22B@sun.com \
--to=florian.bomers@sun.com \
--cc=alsa-devel@lists.sourceforge.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox