Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25689
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.174 as permitted sender)
DomainKey-Status: good
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=c45xsjObEEv6C1iRVYu/oySq1IxqlI5DflRq783afjUBXY5f63gcxnvwMqSIeXldvk7GbPPi5tuWYCdqpr4wv9aHQe+BW9oFCVsXBJFrUzGAIz1Xxd4SFP8Tb11eon9DGpW74Qn9+tNDg7AM2FzZQ8JqBGX8+A8kL+eld0rewJ8=
Message-ID: <fe05d1540609141018v4fa5f7d0q77f5a344b4b04706@mail.gmail.com>
Date: Thu, 14 Sep 2006 19:18:22 +0200
To: "Michael B Allen" <mba2000@ioplex.com>
Cc: internals@lists.php.net
In-Reply-To: <20060914131414.0cef91b2.mba2000@ioplex.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20060914104410.09bdd7f6.mba2000@ioplex.com>
	 <fe05d1540609140749j24ccda71q6bf258eeb7425b41@mail.gmail.com>
	 <20060914131414.0cef91b2.mba2000@ioplex.com>
Subject: Re: [PHP-DEV] Module API Changes
From: pierre.php@gmail.com (Pierre)

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