On 30 July 2017 20:21:01 BST, Stanislav Malyshev wrote:
>Hi!
>
>> My point was that if we were considering a compatibility break
>> anyway, we should look at separating out those common use cases into
>> something higher level.
>
>I'm completely in agreement with you here, except for "compatibilit
2017-07-30 21:41 GMT+02:00 Sara Golemon :
> On Sun, Jul 30, 2017 at 9:22 AM, Anatol Belski wrote:
>>> I think we can handle it in the old-fashioned way now - just notify the RMs
>>> and
>>> clean up the repos.
>>>
>>
> Some scripts for RMs to run periodically will get us 80% of the way
> there, y
On Sun, Jul 30, 2017 at 9:22 AM, Anatol Belski wrote:
>> I think we can handle it in the old-fashioned way now - just notify the RMs
>> and
>> clean up the repos.
>>
>
Some scripts for RMs to run periodically will get us 80% of the way
there, yeah. I don't mind tossing some together and updating
Hi!
> My point was that if we were considering a compatibility break
> anyway, we should look at separating out those common use cases into
> something higher level.
I'm completely in agreement with you here, except for "compatibility
break" part. The good news is that you do not need any compati
Hi!
> This is true within the context of the current "shared nothing"
> design of PHP. There has been talk - and indeed existing
> implementations - of a more event-based system, where this state
> would no longer be naturally global in any sense. But as I
That's fine - but in that design, you sh
On Sat, Jul 29, 2017 at 7:10 PM, Niklas Keller wrote:
> Andrea Faulds schrieb am Sa., 29. Juli 2017, 18:55:
>
> > Hi Craig,
> >
> > Craig Duncan wrote:
> > > On 29 July 2017 at 15:16, Andrea Faulds wrote:
> > >
> > >> Could we not simply make it a flag? e.g.
> > >>
> > >> $bar = json_encode
On 29 July 2017 21:22:30 BST, Stanislav Malyshev wrote:
>> On a slight tangent, I consider $_SERVER to be a broken pile of
>> "we'll just shove this in here and hope for the best", and I will
>> oppose any attempt to convert it into an object which doesn't
>> reorganize its keys to be sane, docume
On 30 July 2017 01:18:56 BST, Stanislav Malyshev wrote:
>Request context is a global state. It is a legit global state -
>everything within the request is executed in the context of the
>request.
This is true within the context of the current "shared nothing" design of PHP.
There has been talk -
Hi Stas,
> -Original Message-
> From: Stanislav Malyshev [mailto:smalys...@gmail.com]
> Sent: Saturday, July 29, 2017 10:16 PM
> To: Anatol Belski ; Sara Golemon ; Remi Collet
>
> Cc: PHP internals
> Subject: Re: [PHP-DEV] Size of release tarballs
>
> Hi!
>
> > Lately there was a disco
> -Original Message-
> From: p...@golemon.com [mailto:p...@golemon.com] On Behalf Of Sara
> Golemon
> Sent: Saturday, July 29, 2017 5:29 PM
> To: Andrea Faulds
> Cc: PHP internals
> Subject: Re: [PHP-DEV] Re: Changes to SuperGlobals for PHP 8 (was: something
> about session_start...)
>
> -Original Message-
> From: kalle@gmail.com [mailto:kalle@gmail.com] On Behalf Of Kalle
> Sommer Nielsen
> Sent: Sunday, July 30, 2017 2:36 AM
> To: Stanislav Malyshev
> Cc: Sara Golemon ; PHP internals
> Subject: Re: [PHP-DEV] Changes to SuperGlobals for PHP 8 (was: something
>
Hi,
So I propose to make the gc_disable function accept one zval reference as
parameter. And if gc_disable get that zval, gc_disable just drop the zval’s
GC_COLLECTABLE flag, which will hint the PHP gc not to trace that zval.
i dont know if this is a good idea or not. But for the "s" in solid,
12 matches
Mail list logo
