Re: EX(scope) removing
| From: | Dmitry Stogov | Date: | Thu, 27 Nov 2014 22:54:59 +0000 |
| Subject: | Re: EX(scope) removing | ||
| References: | 1 2 3 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-79253@lists.php.net to get a copy of this message | ||
Yes, we may store EX(called_scope) in EX(This).value.ce and set another
type and/or flag(s).
But it shouldn't slowdown $this access in _get_obj_zval_ptr_unused() and
other often used functions.
If it's possible, we may try to merge, if not, it doesn't make sense.
Thanks. Dmitry.
On Thu, Nov 27, 2014 at 11:05 PM, Levi Morrison <levim@php.net> wrote:
> On Thu, Nov 27, 2014 at 12:59 PM, Levi Morrison <levim@php.net> wrote:
> >> - try to merge EX(called_scope) and EX(This). Only one of them matters.
> >
> > We could use the void *ptr in a zval (or add it to the available types
> > in the union) and add another flag for zval type. Anyone have an
> > objection with that?
>
> I just noticed we already support putting zend_class_entry* in zvals;
> I'm not exactly sure what the internal representation of This is off
> the top of my head, though; would they be compatible?
>