file structure

Back when we were going to release 3.1, we re-structred all the files. At the same time, we changed the API, and it was a real mess for a long time. Looking back, I can see us facing some of the same problems in the next major release. The lesson that needs to be learnt is to do one thing at a time: change file structure or change API. Doing both at the same time will make the problem bigger than the sum of each problem. I suggest that we change the file structure now, in the php3 tree. IMHO that is the easiest way to make sure further changes are incorporated in the re-structured source tree. We can base the new structure on the ideas in the desolated php31 tree: php3/ext [each extension has its own dir] php3/ext/mysql php3/ext/ldap ... php3/lib/regex php3/lib/win32 php3/main [parser and other vital infrastructure] php3/sapi [server modules] php3 I would like to set up php3/main so you can do a "make install" and install header files, libraries and perhaps some tools to make it possible to compile other applications using PHP code (such as third-party dynamically loadable extensions or PHP RPC servers). When time comes to integrate Zend, that will be easier with this structure. - Stig -- 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