On Nov 12, 2003, at 10:57 AM, Olivier Hill wrote:
Maybe I am mistaken, but I just though of that this morning...
I was reading some slides from Rasmus yesterday, and I was looking at a graph about Op-Codes compilation/cache. I then asked myself how it would be done in PHP5.
Pretty much the same way. None of the architectural changes in ZE2 break tthe fundamental methodologies used by those technologies. In fact, some of the bc breaks in ZE2 (no usage of classes before declaration) make life a bit easier.
Will it be possible with ZE2 to use IonCube PHP4/Zend Cache and APC? If is it pertinent, how could developpers of those extensions port their code to the new ZE2? Would it require some sort of API freeze in ZE2?
They will all need to be ported. Doing it without the internals at least being pseudo-stable is hard (which is why work on porting APC has not begun at all).
If ZE2 needs to be freezed for those extensions to be ported, maybe it would be a good idea to release RC1 ASAP.
The feature freeze has never really applied to internal mechanics of ZE1, I don't assume that it will apply to that of ZE2. Compiler caches hook deeply into the engine - deeper than the api which should be frozen for extension authors. Basically those compiler cache guys are on their own and the ZE2/php5 rc cycle shouldn't particularly concern itself with them.
George
-- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
