Re: Re: [PATCH] Automatic module globals management

From: Date: Thu, 08 Jun 2006 16:46:11 +0000
Subject: Re: Re: [PATCH] Automatic module globals management
References: 1 2 3 4  Groups: php.internals 
Request: Send a blank email to internals+get-23993@lists.php.net to get a copy of this message
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

« previous php.internals (#23993) next »