On Oct 22, 2015 3:45 PM, "Lin Yo-An" wrote:
>
> Hi all,
>
>
> I am looking into zend op_array structure, and few questions raised in my
mind:
>
> 1. Why op_array->refcount uses *uint32 instead of uint32, is there a
reason? if we can replace it with uint32, then we might save one emalloc
call for m
2015-10-22 17:48 GMT+02:00 Julien Pauli :
> This is very tricky use case IMO.
>
> We should absolutely focus on stability, and if we can't find a way to
> make things safe, we forbid them
> for the stability sake. If there are no way to have stable things,
> well, that's pitty but it's like that.
>
On Mon, Oct 19, 2015 at 12:34 PM, Alexander Lisachenko
wrote:
> 2015-10-19 12:19 GMT+03:00 Nikita Popov :
>
>> This change is primarily targeting userland methods, so your use-case is
>> exactly the one this is supposed to prevent. Note that you can still use
>> ->bindTo($object). The only thing y
Results for project PHP master, build date 2015-10-22 05:12:43+03:00
commit: 76a6f28fd856599536f61104f0ebc9eeb11e6ac2
revision date: 2015-10-22 04:01:59+02:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping
2, LLC 45 MB
mem
Hi all,
I am looking into zend op_array structure, and few questions raised in my
mind:
1. Why op_array->refcount uses *uint32 instead of uint32, is there a
reason? if we can replace it with uint32, then we might save one emalloc
call for memory allocation for every op_array allocation?
2. Ther