James, in the past, there was very little interest in a PHP 4
HEAD branch, if you care to recall. Because your rashness
has rendered diff and merge unusable between PHP 4/5, we can
only expect to see even less interest.
Lowering the bar should be the answer to faiding interest,
not raising..
> referred to this change frequently. The problem is that you cannot
> sustain such radical changes in source this way. The differences between
> php3 and php4 are similar to the differences between php4 and php5, with
> many radical changes to the source code being made in php5.
You are confusing two issues here which leads you to a wrong
conclusion.
1.) Moving files inside the repository
PHP 3 contained all extension code in one directory.
These files were moved to separate extension directories
for PHP 4. In such a case, it is impossible to properly
maintain a direct reference between the involved files.
For PHP 5, the extension directories are moved into their
own modules. These are 'projected' back into the php5
module by using CVS tricks. The same tricks can be used
for a php4 or php-src module. As such, there is no
visible difference from the outside at all, and hence no
restructuring from a CVS user perspective.
2.) Source code changes
I'd estimate that >90% of the non-engine code remains the
same.
Thus, I fail to see any of the perceived radical changes.
An evolutionary step is the perfect candidate for a new
branch; it does not warrant a repository split.
- Sascha
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
