Internals,
While cleaning up some PRs I was prompted to re-visit one I had
outstanding about exception-throwing behaviour when redefining
constants, this applies to functions like define and language syntax
constructs such as const.
There have been a few discussions in the past about the
Hello,
We are using PHP for our application backends, this works very well as we have
developed s imple way to clone them with minimal effort(they can be very
similar). For our orchestration we are using Kubernetes (>= 1.21). Our
application pod generally contains NGINX + php-fpm and fluentbit
Hi Internals,
I have opened voting on https://wiki.php.net/rfc/mysqli_support_for_libmysql
Voting ends in 2 weeks.
Kind regards,
Kamil
On 22.01.2022 at 17:18, Rowan Tommins wrote:
> On 22/01/2022 15:30, Christoph M. Becker wrote:
>
>> If you trigger the garbage collector manually (i.e. call
>> gc_collect_cycles() after unset($callback)), the loop terminates right
>> away. I'm not sure why it doesn't without manually triggering
On 22/01/2022 15:30, Christoph M. Becker wrote:
If you trigger the garbage collector manually (i.e. call
gc_collect_cycles() after unset($callback)), the loop terminates right
away. I'm not sure why it doesn't without manually triggering the GC.
Most values are freed as soon as their
> On Jan 21, 2022, at 4:31 AM, Dominic Grostate
> wrote:
>
> Hi Internals,
>
> I'd like to express my interest in a possible feature concerning weak
> references. Currently closures created within a class appear to
> contain a reference to the object that created it. This is of course
>
On 21.01.2022 at 11:31, Dominic Grostate wrote:
> I'd like to express my interest in a possible feature concerning weak
> references. Currently closures created within a class appear to
> contain a reference to the object that created it. This is of course
> necessary in order for the closure to
