Re: [RFC] FPM INI syntax
2010/4/13 Zeev Suraski <zeev@zend.com>:
> What he means is that it'll be implemented in the custom code responsible
> for parsing fpm.ini, and not in the ZE .ini parser which would be the layer
> below it. Implementing include() can be done at either layer. If it's
> implemented at the bottom layer (ZE) then it'll transparently effect any and
> all .ini's - not sure we want that (maybe). If we implement it at the top
> layer - the custom code that's responsible for fpm.ini, then it will be
> entirely specific to it and won't effect php.ini behavior in any way
> (exactly like the support for the 'extension' keyword is implemented for
> php.ini, but not for any other .ini's - because it's at the top custom-code
> layer).
I think generic include capability for php .ini files would be quite handy.
Thread (34 messages)