Johannes Schlüter wrote: > Hi all, > > recently there were quite a few proposals about stuff for 5.3. If we > implement > them all we won't finish in a "soonish" time and we get new ideas postponing > the 5.3 release therefore the following: > > - Scanner based on re2c: > Going to re2c promises to make maintenance simpler and increase the parsers > performance. Currently the prototype does not provide support for Zend > multibyte mode. This seems doable within April. Hence I ask for finishing > by end of April the latest. Once that is done we will go over to a freeze > and > switch to bug fixing only mode. > If this is done sooner than we'll freeze sooner, too. If there are delays > we'll freeze anyways and use the scanner for a later release. > > - bundling pecl/intl > According to Stas it's ready for being bundled and was voted in. The only > question I see there is the "how to bundle it". There we should definitely > find a better thing than symlinking around on the CVS server, an option > might be to to switch to subversion and use svn:externals or keeping stuff > in pecl and then having some scripts (maybe part of buildconf/the release > scripts) fetching them into a checkout. Just ideas ... For the moment > symlinking might be the best. > > - bundling pecl/phar > Lots of work has been done there, I'd like to have it in, general PECL > discussion: See above.
Hi, Just a quick note: I'd like to consider another possible approach, having pecl/phar synced from stable pecl release. I think this can be done via a simple configure script that wgets the latest stable and uses a clever little PHP_Archive-based phar to extract the source files. There are of course other ways to do this that may be better than my quick-and-dirty description, but it is certainly possible. As the primary maintainer of the PEAR installer, this would make it easier for me to fix issues found in this process. Because phar is new, this will give more wiggle room for experimenting, and what we figure out could then be used to allow the current vaporware proposal of moving all exts to pecl. I am also fine with symlinking until this can be perfected, as it is just an idea to be implemented right now. phar is in a state of slight flux: if stream wrappers get supported inside include_path, it would change a lot of the implementation stuff I've needed to do, and greatly simplify phar, so it will continue to improve with this addition. Greg -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php