Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25688 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 72121 invoked by uid 1010); 14 Sep 2006 17:15:22 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 72101 invoked from network); 14 Sep 2006 17:15:22 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Sep 2006 17:15:22 -0000 Authentication-Results: pb1.pair.com smtp.mail=mba2000@ioplex.com; spf=permerror; sender-id=unknown Authentication-Results: pb1.pair.com header.from=mba2000@ioplex.com; sender-id=unknown Received-SPF: error (pb1.pair.com: domain ioplex.com from 66.220.1.142 cause and error) X-PHP-List-Original-Sender: mba2000@ioplex.com X-Host-Fingerprint: 66.220.1.142 www.ioplex.com Linux 2.4/2.6 Received: from [66.220.1.142] ([66.220.1.142:1229] helo=www.ioplex.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id EA/0E-45066-70E89054 for ; Thu, 14 Sep 2006 13:15:22 -0400 Received: from quark.foo.net (c-69-142-196-170.hsd1.nj.comcast.net [69.142.196.170]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by www.ioplex.com (Postfix) with ESMTP id 0BC9B42C26; Thu, 14 Sep 2006 13:14:43 -0400 (EDT) Date: Thu, 14 Sep 2006 13:14:14 -0400 To: Pierre Cc: internals@lists.php.net Message-ID: <20060914131414.0cef91b2.mba2000@ioplex.com> In-Reply-To: References: <20060914104410.09bdd7f6.mba2000@ioplex.com> X-Mailer: Sylpheed version 1.0.6 (GTK+ 1.2.10; i386-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Module API Changes From: mba2000@ioplex.com (Michael B Allen) On Thu, 14 Sep 2006 16:49:16 +0200 Pierre wrote: > Hello, > > On 9/14/06, Michael B Allen 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. Is it possible to load a module compiled with a ZEND_MODULE_API_NO that differs from the one PHP was compiled with? Is it possible for a module compiled with debugging to be loaded in a debug build of PHP? 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). Has the module API changed in 5.2? Thanks, Mike -- Michael B Allen PHP Active Directory SSO http://www.ioplex.com/