Re: Re: cvs: php4 / Makefile.global
| From: | Yasuo Ohgaki | Date: | Fri, 25 Oct 2002 03:36:22 +0000 |
| Subject: | Re: Re: cvs: php4 / Makefile.global | ||
| References: | 1 2 3 4 5 6 7 8 9 10 11 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-90093@lists.php.net to get a copy of this message | ||
Sander Roobol wrote:
On Thu, Oct 24, 2002 at 11:59:19AM -0400, Jon Parise wrote:Of course, I know that. But my points are - run-tests.php itself is not test script, but phpt is. - with specific ini, we can get rid of code aren't needed - we don't have to care about careless patches, and say 'Hey your patch does not work with my php.ini". - things are easier with certain ini. - etc, etc. So far, I didn't see any good point using various php.ini settings for run-tsets.php. Person, who get rid of the setting and insist specifying php.ini is not worth, even cannot find and fix problem with php.ini-recommended. Better choice is obvious, isn't? -- Yasuo Ohgaki- Change the compiled default value for output_buffering to 0. - Allow output_buffering to be set by ini_set(). - Specify 'output_buffering = 0' via the -D command line optionCan't we just flush all the open output buffers? Something like this: while(ob_get_level()) ob_end_clean();for run-tests.php.- Pass a php.ini configuration file to run-tests.php using -C.