Hi!
interface but that wasn't really a good idea. So I came up with a new
interface and all that this would break is stuff like Phar (well there is
If it breaks phar, it may break others too... Anyway, good description
of what was changed won't hurt.
2. PHP 5.x is same-major branch, where you are not expected to have to
change your system in order to upgrade.
Oh since when? Where did you read that?
Since forever, that's why we have major and minor versions.
I don't care at all. So far the plan was to bring in ICU and there is no
In PHP 6, not 5.3.
In software there is nothing like 100% Or is everything you work on bug
free? Mine isn't. It took me more than two years to make re2c ready for
this task (take this in whatever way you feel).
I'm not talking about bugs. I'm talking about having compatible engine
implementation. Nobody would require 100% bug-free code, it's not
realistic. Requirement is that scripts that run on 5.2 would run on 5.3,
not counting bugs. I guess you agree having no multibyte support does
not really qualifies as "bug" :) So we are talking about if putting it
in now might hurt 5.3 release process by postponing it for a long time
or not. If not - great.
How so? We don't use git or any other CMS that allows merging at all. I
CVS allows merging. I did it a lot of times. Of course, there could be
conflicts, but the engine is quite static now, so I don't foresee a lot
of them.
--
Stanislav Malyshev, Zend Software Architect
[EMAIL PROTECTED] http://www.zend.com/
(408)253-8829 MSN: [EMAIL PROTECTED]
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
