2010/4/15 Zeev Suraski <z...@zend.com>: > At 14:30 15/04/2010, Ferenc Kovacs wrote: >> >> Yep, this what I'm trying to say. I thought that the include parameter in >> the global.ini is just a normal config variabla, which isn't interpreted by >> the php parse ini method, only just tells the fpm, to include that files >> manualy and merge the contents of that files into the original configuration >> parsed from the global.ini. >> But as far as I understand the patch and the discussion, it seems that >> Jerome proposed to change the internal working of the ini parsing, to add >> general support for includes.
Not especially. I always wanted to implement includes into FPM and not widely into zend_ini_parser. > > Actually as far as I understand what you wrote in the 1st paragraph is > exactly what was planned. There weren't any plans to touch the .ini parser > itself in any way. > What I said beforehand is that there are two ways to implement include: > 1. In the .ini parser; That means it'll work for anything that uses the > .ini parser, including php.ini, fpm.ini, parse_ini_file(), etc. It's a huge change, it's has to be tested a lot ... too much complicated > 2. In the FPM code that uses the .ini parser; Much like it pays attention > to 'daemonize' and 'error_log', it can pay attention to 'include'. The easiest et most logical solution. FPM wants include in its ini configuration file and it's the only part of PHP which need that at the moment. Since FPM has been integrated info PHP, it never touched something but its own code ... try to stay that way ! -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
