Re: file structure

> About changing the API and directory structure at the same time, I'm not > sure if that was *the* problem of php 3.1 and the key to its lingering, I > happen to think that it didn't play a major role there. As long as we keep > the tree at a compilable state at all times, we can apply different kinds > of patches (structure and API) without significant problems. Another > difference from 3.1 is that I expect that php3 development would pretty > much slow to a halt once the php4 tree is available. It has definitely > been my recommendation all along, and still is. Until there is a completely open cvs tree, I don't see that happening. The modules will keep evolving and new ones will get added. Even when there is an open cvs tree, people are going to want to build modules that work with the existing php3 installed base. So we are going to have to do something to try to bring bring these two trees closer together. Perhaps a way to build a php3-compatible dynamic extension from the php4 tree, or maybe a backport of the dynamic module building code into php3. We can't expect people to just sit still for a few months and not do anything. -Rasmus -- PHP Development Mailing List http://www.php.net/ To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net For help: php-dev-help@lists.php.net