Re: output buffering in CLI script.
| From: | Jim Lucas | Date: | Fri, 29 Feb 2008 04:00:01 +0000 |
| Subject: | Re: output buffering in CLI script. | ||
| References: | 1 2 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-270690@lists.php.net to get a copy of this message | ||
Casey wrote:
On Thu, Feb 28, 2008 at 3:39 AM, Jochem Maas <jochem@iamjochem.com> wrote:nope, because it comes before the <?php in the file If it were after the <?php then it would be considered a comment. Jimhi there, I can't seem to manage to buffer output (of an included file) in a CLI script, the following does not work:I use Windows, so I don't need the shebang line. But if I'm correct and the shebang line is: #!/usr/bin/php , shouldn't it be considered a comment, because of the "#"?// buffer output so we can avoid the shebang line being output (and strip it from the output we log) $oldIFvalue = ini_set('implicit_flush', false); ob_start();if (!@include $script) { ob_end_clean(); } else { $output = explode("\n", ob_get_clean()); if ($output[0] && preg_match('%^#!\/%', $output[0])) unset($output[0]); }ini_set('implicit_flush', $oldIFvalue);the reason I'm wanting to do this is, primarily, in order to stop the shebang line that *may* be present in the included script from being output to stdout.