Hello, > new stage won't ever work, of course. If there's an extension which > uses INI_STAGE_ACTIVATE and needs to support new htaccess stage, it > can be fixed in source so check for this stage too - but I didn't see > such extensions yet. Well I actually know such an extension ;) It is called Suhosin. Well but that support was broken anyway. The sense of the INI_STAGE_ACTIVATE check was to give the admin the possibility to forbid groups of INI_PERDIR to be configured by htaccess. (without setting a default with php_admin_value in httpd.conf for all that should not be under user control.) Actually before your commit that of course never worked correctly and broke INI_PERDIR completely.
Now with the new commit I can implement it correctly. However the problem stays that actual binary compatibility is not broken by the check but any extension relying on the new feature might not work correctly. However I think for my purposes I can simply define the INI_STAGE_HTACCESS constant if it does not exist and simply tell everyone to upgrade to a bugfixed version. Haha. Stefan -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
