Am Freitag, 15. Mai 2009 schrieb Michael Shadle:
Hallo,
> There's gotta be a time in the natural evolution to "cut the cord" so
> to speak - Python just launched 3.0 and dropped backwards
> compatibility. Why can't PHP do the same in 6.0? :) (Or 5.3 for all I
> care. But it really should align with a major revision #)
Splitting PHP in 3 independent parts could help solving the
backwards problem.
- Library (Functions, Methods)
- Virtual Machine (Zend Engine)
- Compiler for PHP 5.2, PHP 6, ...
Library
|
VM
|
P-Code/Bytecode
/ | \
/ | \
5.2 5.3 6.0 ... compiler
So a system could contain a compiler for each major
PHP version. Sourcecode written for PHP 5.2 will
use PHP compiler 5.2, sourcecode for PHP 6.0 will use
PHP compiler 6.0, ... No backwards problem for existing
code.
It's still necessary to update 5.2 code to use it
with the PHP 6.0 compiler but the existing code
does not prevent to use PHP 6.0 now for new scripts and
classes. And this is IMO easier then using (fast) CGI or
multiple instances of a webserver to have different
versions of PHP on one server.
There could also be different major versions of
the library.
tschuess
[|8:) http://www.sven-drieling.de/
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
