Module activation order in php_request_startup()

Hi, Currently activation functions are called in the following order on request startup: 1. zend_activate() 2. sapi_activate() 3. php_hash_environment() 4. zend_activate_modules() Is there any good technical reason behind this order? I don't think it does make much sense because php_hash_environment() can call input handlers before the modules providing those handlers are initialised. It also resulted in a fatal bug in mbstring reported recently in the Japanese user's mailing list; some settings kept in the module globals leak over requests. Regards, Moriyoshi