[Fwd: use new API ?]
Please apologize for the repetition of my question. I probably don't have to tell you that in commercial software engineering I have to deal with hard dead-lines and longer development and test cycles. I guess most of you don't even care... but I think it would be a pity for many people if Sun's Java still wouldn't support ALSA in the next years, just because I did not choose the 0.9.0-compatible way.
If there are other reasons why answers were pretty rare to my following question, please tell me. Being a OSS developer myself I know that commitment is unpopular (and "urgent" requests even more so), but then I'd appreciate at least to hear that you don't have any plans for 0.9.0rc5's compatibility with future versions.
--------
Is it more likely that
1) the already changed function prototypes, which are usable by defining ALSA_PCM_NEW_HW_PARAMS_API, change in future,
or
2) 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 <[email protected]>
Organization: Sun Microsystems, Inc.
To: ALSA devel <[email protected]>
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
Signature · 10 lines
Florian Bomers Java Sound Java Software/Sun Microsystems, Inc. http://java.sun.com/products/java-media/sound/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf
Quoted 13 lines · Florian Bomers
Please apologize for the repetition of my question. I probably don't have to tell you that in commercial software engineering I have to deal with hard dead-lines and longer development and test cycles. I guess most of you don't even care... but I think it would be a pity for many people if Sun's Java still wouldn't support ALSA in the next years, just because I did not choose the 0.9.0-compatible way.
If there are other reasons why answers were pretty rare to my following question, please tell me. Being a OSS developer myself I know that commitment is unpopular (and "urgent" requests even more so), but then I'd appreciate at least to hear that you don't have any plans for 0.9.0rc5's compatibility with future versions.
Quoted 6 lines
--------
Is it more likely that
1) the already changed function prototypes, which are usable by defining
ALSA_PCM_NEW_HW_PARAMS_API, change in future,
If you use this define, your application will work with next major ALSA release (probably 1.0). Note that we have also ALSA_PCM_NEW_SW_PARAMS_API.
Quoted 2 lines
or
2) that the deprecated functions will be removed ?
Yes, we'll remove deprecated functions, but not for 0.9.
Quoted 3 lines
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 ?
I hope that this change was the last change before 0.9.0final, but as you seen, we are trying to retain compatibility. So, old programs will work with newer ALSA libraries (at least for major ALSA releases) - note that it does not work in opposite way - programs linked with newer libraries can have trouble with older libraries.
I am sorry for late reply.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
That's useful and very promising news! Thank you very much.
Florian
Quoted 40 lines · Jaroslav Kysela
Quoted 4 lines
Is it more likely that
1) the already changed function prototypes, which are usable by defining
ALSA_PCM_NEW_HW_PARAMS_API, change in future,If you use this define, your application will work with next major ALSA release (probably 1.0). Note that we have also
ALSA_PCM_NEW_SW_PARAMS_API.Quoted 2 lines
or
2) that the deprecated functions will be removed ?Yes, we'll remove deprecated functions, but not for 0.9.
Quoted 3 lines
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 ?
I hope that this change was the last change before 0.9.0final, but as you seen, we are trying to retain compatibility. So, old programs will work with newer ALSA libraries (at least for major ALSA releases) - note that it does not work in opposite way - programs linked with newer libraries can have trouble with older libraries.
I am sorry for late reply.
Jaroslav
-----
Jaroslav Kysela <[email protected]>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Alsa-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
Signature · 10 lines
Florian Bomers Java Sound Java Software/Sun Microsystems, Inc. http://java.sun.com/products/java-media/sound/ ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf