Re: Re: your mail
| From: | Zeev Suraski | Date: | Sat, 15 May 1999 22:42:47 +0000 |
| Subject: | Re: Re: your mail | ||
| References: | 1 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-5655@lists.php.net to get a copy of this message | ||
While this can be easily done using output buffering, it's not out of the
question to directly support redirection of the output. PHP 4.0's output
mechanism is centralized, and changing where output goes involves changing
exactly one function pointer.
Zeev
On Sun, 16 May 1999, Sascha Schumann wrote:
> On Sun, May 16, 1999 at 01:17:20AM +0300, Zeev Suraski wrote:
> > It's done. PHP 4.0 supports output buffering. Using output buffering,
> > you can easily collect your output into a standard PHP variable, and then
> > feed it to a function or a file or whatever you have in mind.
> >
> > Zeev
>
> In the same sense, it would be useful, if there
> would exist a standard way of referring to
> stdin/stdout/stderr. I usually end up in opening
> the respective /dev/std* but this is indoubtly
> unportable.
>
> Additionally, having something like Perl's
> select() function would be cool which sets the
> standard output channel (maybe this is already
> covered by "output buffering").
>
> E.g.
>
> $some_fd = fopen(...,"w");
> select($some_fd);
> print "file content";
>
> --
>
> Regards,
>
> Sascha Schumann
> Consultant
>
--
-----------------------------------------------------
Zeev Suraski <zeev@zend.com>
For a PGP public key, finger bourbon@netvision.net.il
--
PHP Development Mailing List http://www.php.net/
To unsubscribe send an empty message to php-dev-unsubscribe@lists.php.net
For help: php-dev-help@lists.php.net