Re: Reflection to remove final
| From: | Jan Dolecek | Date: | Tue, 17 Jan 2012 23:00:09 +0000 |
| Subject: | Re: Reflection to remove final | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-57404@lists.php.net to get a copy of this message | ||
This issue seems much more complicated than I thought. We'll need to
consider all cases which could cause troubles and have a solution for
them.
Namely:
- rewriting permanent structures for internal classes, which are
being kept between requests, must be avoided
- races in threading models
- rewriting in bytecode caches must be avoided
- anything else in mind?
I'll try to think about it, but I'm not that experienced with php
internals, so any suggestions welcome.
Jan Dolecek
juzna.cz@gmail.com
On Tue, Jan 17, 2012 at 11:21 PM, Stas Malyshev <smalyshev@sugarcrm.com> wrote:
> Hi!
>
>
>> This doesn't seem right. Correct me if I'm wrong: for internal classes,
>> their data structures are allocated permanently, so I'd say the effects of
>> removing the flag would be permanent (i.e., would affect subsequent
>> requests). And for threaded builds this could cause races between the
>> threads.
>
>
> It'd probably also mess up bytecode caches, since they permanently store
> class definitions.
> --
> Stanislav Malyshev, Software Architect
> SugarCRM: http://www.sugarcrm.com/
> (408)454-6900 ext. 227
>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>