On 09/08/02, "Tony Leake" <[EMAIL PROTECTED]> wrote:
> Thanks for the suggestion to put this into Pear. I have subscribed to
> the dev list and I'll see what they think :)
You can place it into pear/PECL; which is going to be the definitive
place for C based PHP extensions in the not too distant future.
> eci_init();
> eci_command();
> eci_error();
> audio_playfile();
^
I think we would like an underscore here: audio_play_file
> audio_convert_file();
> audio_new_chain();
That fits with our naming conventions; however, I think that Andi
was hoping you would post a little bit info about the parameters
of the main functions that you expect people to use; something like
this:
bool audio_play_file(string filename);
Plays an audio file to the default sound output device
Or is it more advanced:
bool audio_play_file(resource device, string filename)
Plays an audio file on the specified device
> 3) will be midi functions,this is a long way off yet so I haven't given
> it too much thought yet. Also it is likely to be a separate module as it
> will need to link against a separate library and I can't think of any
> PHP modules that link against 2 libs.
I don't think there is a need to make this into two separate extensions
(it just makes things harder for the end user) - you can link to as many
libs as you like from your extension.
> One last question. I'm sure I read somewhere that the PHP licence is not
> compatible with the GPL. Is this true? If so what do I need to do is a
> simple agreement from the ecasound maintainer enough or will he need to
> release it under the PHP licence as well?
You can use any license you like when your code is in pear/PECL (so long
as it allows "joe public" to download your code from the php.net server).
The license incompatibility only affects whether your extension can be
bundled/distributed with the PHP core. (as was the case with my mailparse
extension...)
--Wez.
--
PHP Development Mailing List <http://www.php.net/>
To unsubscribe, visit: http://www.php.net/unsub.php
