The documentation doesn't really cover this, so I'm hoping it's OK to ask here.
The FFI docs say that for web requests, you really really ought to use
preloading and then load/scope to manage an FFI library because it's going to
be too slow to link up otherwise. See the example here:
On 19/12/2019 12:51, Christoph M. Becker wrote:
On 20.11.2018 at 11:26, Rowan Collins wrote:
It seems to me that *neither* extension is properly maintained right now
(the with-a-d extension has recent releases, but all wrapping an abandoned
upstream library); so if the without-a-d extension
On 20.12.2019 at 10:39, Peter Cowburn wrote:
> On Fri, 20 Dec 2019 at 09:31, Rowan Tommins wrote:
>
>> On Fri, 20 Dec 2019 at 08:37, Christoph M. Becker
>> wrote:
>>
>>> Maybe a sensible compromise would be to assemble a detailed list of
>>> these changes, and to hand it over to the doc team at
On Fri, 20 Dec 2019 at 09:31, Rowan Tommins wrote:
> On Fri, 20 Dec 2019 at 08:37, Christoph M. Becker
> wrote:
>
> > Maybe a sensible compromise would be to assemble a detailed list of
> > these changes, and to hand it over to the doc team at some point, so
> > that the manual pages could
On Fri, 20 Dec 2019 at 08:37, Christoph M. Becker wrote:
> Maybe a sensible compromise would be to assemble a detailed list of
> these changes, and to hand it over to the doc team at some point, so
> that the manual pages could (hopefully) be updated in time just before
> PHP 8.0.0 will be
On 20.12.2019 at 00:05, Máté Kocsis wrote:
> Although, the only problem I have with including every promoted warning in
> the upgrading notes
> is that doing so would possibly cannibalise it as there are dozens (if not
> hundreds) of
> promotions that have already taken place...
>
> Nevertheless,
