On Mon, May 01, 2006 at 06:48:11AM -0500, Kevin P. Fleming wrote: >> This moving helps to minimize duplicate code and improve API stability >> without affecting development speed. KPF> This is incorrect. As soon as 'struct ast_channel' is part of the KPF> library's API (as it would have to be), then we cannot make changes to KPF> the channel structure without having to increase library versions and KPF> modifying all the modules to require that version. This will take KPF> significant amounts of time.
Some modules doesn't need to work with this struct directly. KPF> I don't see any value in having modules that are usable across Asterisk KPF> versions in binary form; this is open source software, and nearly all KPF> modules available for it should only need source-level compatibility, KPF> not binary compatibility. It need for linux distributions, for updating third part modules independent with asterisk. -- JID: [EMAIL PROTECTED] ICQ: 58417635 (please, use jabber, if you can) http://freesource.info/ _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- asterisk-dev mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-dev
