Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25690
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain zend.com from 192.38.9.232 cause and error)
Message-ID: <064c01c6d822$d37bc730$6602a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Pierre" <pierre.php@gmail.com>,
	"Michael B Allen" <mba2000@ioplex.com>
Cc: <internals@lists.php.net>
References: <20060914104410.09bdd7f6.mba2000@ioplex.com> <fe05d1540609140749j24ccda71q6bf258eeb7425b41@mail.gmail.com> <20060914131414.0cef91b2.mba2000@ioplex.com> <fe05d1540609141018v4fa5f7d0q77f5a344b4b04706@mail.gmail.com>
Date: Thu, 14 Sep 2006 19:25:49 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Module API Changes
From: steph@zend.com ("Steph Fox")

Hi Michael, Pierre -

Erm, no they aren't in the upgrade guide, because the upgrade guide is aimed 
at user issues and this was seen primarily as an extension author issue. Do 
people generally think the module and extension API bumps should be in 
there?

- Steph

> Hello,
>
> On 9/14/06, Michael B Allen <mba2000@ioplex.com> wrote:
>> On Thu, 14 Sep 2006 16:49:16 +0200
>> Pierre <pierre.php@gmail.com> wrote:
>>
>> > Hello,
>> >
>> > On 9/14/06, Michael B Allen <mba2000@ioplex.com> wrote:
>> >
>> > > Are there any other module API changes between 4 and the current 
>> > > version
>> > > of PHP that would cause my module to fail to load?
>> >
>> > PHP internals API has many changes between two major versions. Don't
>> > expect a module compiled for php4 to be loaded smoothly in php5, the
>> > same applies from one minor version to another. You have to provide a
>> > binary per minor version, and for debug or non debug builds, like any
>> > other DLL/so.
>> >
>> > (5.0 and 5.1 are php5 minor versions, for example)
>>
>> Sorry, I meant to say minor version. So the minor version will change
>> if the module API changes?
>>
>> Our module compiles without modifcation with 4, 5.0, and 5.1.
>
> Some of mines too. The problem is not to compile but to load it.
>
>> Is it possible to load a module compiled with a ZEND_MODULE_API_NO that
>> differs from the one PHP was compiled with?
>
> No
>
>> Is it possible for a module compiled with debugging to be loaded in a
>> debug build of PHP?
>
> Neither
>
>> It's not a horribly big deal to ship 3 modules but it would be nice if
>> our package had a level of forward compatibility (e.g. worked with a
>> new snapshot that introduced a moduel API change).
>
> If it a snapshot have a new API, it will also have a new API version
> and will be available in  a new minor/major PHP version.
>
>> Has the module API changed in 5.2?
>
> Yes, if not it will still be 5.1.x. I think the changes will be
> explained in the README.UPDATE_5_2 file in CVS, or they are already
> in.
>
> --Pierre
>
> -- 
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>