Marcus Boerger wrote:
- Improved php.ini handling: (Jani)
- . Added ".htaccess" style user-defined php.ini files support for CGI/FastCGI
+ . Added ".htaccess" style user-defined php.ini files support for CGI/FastCGI.
. Added support for special [PATH=/opt/httpd/www.example.com/] and
[HOST=www.example.com] sections. Directives set in these sections can
not be overridden by user-defined ini-files or during runtime.
- . Added better error reporting for php.ini syntax errors
- . Allowed using full path to load modules using "extension" directive
- . Allowed "ini-variables" to be used almost everywhere ini php.ini files
- . Allowed using alphanumeric/variable indexes in "array" ini options
+ . Added better error reporting for php.ini syntax errors.
+ . Allowed using full path to load modules using "extension" directive.
+ . Allowed "ini-variables" to be used almost everywhere ini php.ini files.
+ . Allowed using alphanumeric/variable indexes in "array" ini options.
. Added 3rd optional parameter to parse_ini_file() to specify the scanning
mode of INI_SCANNER_NORMAL or INI_SCANNER_RAW. In raw mode option values
- and section values are treated as-is
- . Fixed get_cfg_var() to be able to return "array" ini options
+ and section values are treated as-is.
+ . Fixed get_cfg_var() to be able to return "array" ini options.
How much of what I did to the ini scanner actually is left since it's conversion
to RE2C? For example that syntax error (and error handling in general)..?
--Jani
--
PHP CVS Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php
