Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25684
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain ioplex.com from 66.220.1.142 cause and error)
Date: Thu, 14 Sep 2006 10:44:10 -0400
To: internals@lists.php.net
Message-ID: <20060914104410.09bdd7f6.mba2000@ioplex.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: Module API Changes
From: mba2000@ioplex.com (Michael B Allen)

I see the module API has changed between 5.0 and 5.1. This caused my
module to fail to load with:

PHP Warning: PHP Startup: z\x17\xfc\xb6d\x12\xfc\xb6: Unable to initialize module
Module compiled with module API=20041030, debug=0, thread-safety=0
PHP    compiled with module API=20050922, debug=0, thread-safety=0
These options need to match
in Unknown on line 0

Obviously this is problematic when shipping binaries. Basically I now
have modules for 4, 5.0, and 5.1 in my installation package and look at
phpversion() to determine which one to install.

Are these module changes very common?

Is there an easier way to ship module binaries?

Is the major verion number guaranteed to change when the module API
changes?

Are there any other module API changes between 4 and the current version
of PHP that would cause my module to fail to load?

Thanks,
Mike

-- 
Michael B Allen
PHP Active Directory SSO
http://www.ioplex.com/