Re: Module API Changes

Huh? The question was about module API change, which is transparent to anyone mixing and matching PHP and module versions (which incidentally they shouldn't be doing in the first place). The extension API doesn't matter to anyone but extension authors... and actually I can't remember if the code for that retained BC off-hand too... need to check... There were a handful of minor API breakages that I vaguely remember fixing for PHP-GTK back then, but they came under the 'extension API bump' mbrella - in other words, they were ignored in their own right. Again, these were things that would be evident to an extension maintainer rather than an end user - and everything there would be better covered in README.EXTENSIONS than in an upgrade file aimed at end users, where it just looks scary and oblique. OK so I'll update that file tomorrow and reference it from the upgrade file. Any objections to that approach? - Steph ----- Original Message ----- From: "Pierre" <pierre.php@gmail.com> To: "Steph Fox" <steph@zend.com> Cc: "Michael B Allen" <mba2000@ioplex.com>; <internals@lists.php.net> Sent: Thursday, September 14, 2006 8:14 PM Subject: Re: [PHP-DEV] Module API Changes

Hello, On 9/14/06, Steph Fox <steph@zend.com> wrote:

OK, has anyone enough time to commit this please? I left the extension API change out of it though (the ME_* support) - does that really need to go in there too?

This thread justifies the addition (and all other about the same topic :).