"none" as an INI value - RFC

I think that the use of 'none' as an INI value is wrong. Today, there are plenty of checks in plenty of different places that check whether a given INI value is equal to "none", in PHP's runtime, and if it is, they regard it as an empty string. My guts tells me its wrong, because it prevents you from using the perfectly-valid 'none' string as a value. What I propose is the following: - I'd make 'none' a keyword that the php.ini processor would understand as an empty string. - Everyone would nuke their specialized code that checks for "none" This would give us two benefits: 1. It'll be possible to use the string 'none' as a value, if you enclose it in double quotes, much like Off means 0, but "Off" means "Off" (in php.ini). 2. It'll be much quicker, since it'll only happen once, when reading the php.ini file. Comments? Zeev -- Zeev Suraski <zeev@zend.com> http://www.zend.com/