On 26 Jul 2017, at 22:57, ?????? <0...@lvht.net> wrote:>> There is a way to work around: just call gc_disable(). But this means >> dealing with side effects of the engine in userland. Moreover, this also >> means leaking memory, since meanwhile roots are not populated.
>Maybe we could make gc_disable accept one reference zval as parameter, and >clear the GC_COLLECTABLE flag of zval.value->gc.u.v.flags. So, this zval >will never be put into gc root list. I don't think it's a good idea to expose such an internal detail to userland. The more we expose, the more limits we will face in the future if we want to make some changes. best regards, CHU Zhaowei
