Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:23993
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <100601c68b1b$0d9f9d60$6602a8c0@foxbox>
Reply-To: "Steph Fox" <steph@zend.com>
To: "Sara Golemon" <pollita@php.net>,
	"\"Dmitry Stogov\"" <dmitry@zend.com>
Cc: "Ilia Alshanetsky" <ilia@prohost.org>,
	"Andi Gutmans" <andi@zend.com>, <internals@lists.php.net>
References: <000001c68af5$50876930$6e02a8c0@thinkpad> <003f01c68b13$4f9ce680$88051fac@OHRLVN4523SG> <0fd201c68b16$2134af00$6602a8c0@foxbox> <006201c68b1a$b9338610$88051fac@OHRLVN4523SG>
Date: Thu, 8 Jun 2006 18:46:11 +0200
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="Windows-1252";
	reply-type=response
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] Re: [PATCH] Automatic module globals management
From: steph@zend.com ("Steph Fox")

>> Yes, I know. But altered modules won't be able to use older versions of 
>> PHP readily, and that's going to be a real problem in PECL - especially 
>> if this goes into 5_2 branch.
>>
> For the modules which are part of the core distribution this is a 
> non-issue as they're branched.  For PECL modules this is the same "how old 
> of a PHP version am I (as the package maintainer) willing to support?". 
> That package maintainer can: (A) Not use the new API, (B) Wrap up some 
> #ifdef's, or (C) Use the new API exclusively and eschew pre-5.2.

Right, and that's why I think it's problematic to have such a major change 
in the API, because (A) and (C) are the likeliest outcomes - (B) is 
virtually unmanageable. Take a look at what it takes for an extension to 
adapt to this, and then imagine all of it #ifdef'd....

- Steph