Re: Bug 61272
| From: | Yasuo Ohgaki | Date: | Thu, 06 Dec 2012 08:32:33 +0000 |
| Subject: | Re: Bug 61272 | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-64172@lists.php.net to get a copy of this message | ||
2012/11/29 Michael Wallner <mike@php.net>:
> On 29 November 2012 08:00, Yasuo Ohgaki <yohgaki@ohgaki.net> wrote:
>> However, new code encapsulate output globals. (I mean internally)
>> It would be nice for my extension if output globals are exposed.
>
> This was changed intentionally, why would you need OG what the API
> does not provide?
>
>> Exposing output global is not mandatory, though.
Encapsulation is great for ordinary use, but I have extension that
records PHP internal activities. It also records and override some
contents of output global.
I haven't thought what API would be needed, I'll look into current code
later and what API is needed.
Regards,
--
Yasuo Ohgaki
yohgaki@ohgaki.net