Hi,
I wanted first to know if php source code can welcome oses specific
features or should it remain as separated php modules ?
For instance awhile ago I implemented a wrapper around OpenBSD's pledge for
suhosin (php 5.x series) here
https://github.com/sektioneins/suhosin/blob/master/pledge.c
T
Just another poke to surface it, in case this should be merged into the 7.0
branch as well :)
https://bugs.php.net/bug.php?id=74250
> On 19. Mar 2017, at 23:39, David Zuelke wrote:
>
> Thanks for the fixes, Nikita!
>
> Will they be merged to the PHP-7.0 branch as well?
>
>
>> On 14 Mar 201
On 27/03/2017 19:28, David CARLIER wrote:
I wanted first to know if php source code can welcome oses specific
features or should it remain as separated php modules ?
Hi David,
I think there is not really a distinction between "PHP source code" and
"separated modules", since pretty much everyt
Results for project PHP master, build date 2017-03-26 20:29:51-07:00
commit: 56269af
previous commit:1686183
revision date: 2017-03-24 12:25:27+00:00
environment:Haswell-EP
cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores,
stepping 2, LLC 45 MB
Hello PHPeeps,
There hasn't been much discussion around the proposed feature, and I've
interpreted it as a good sign :P It is not a super important change but it
has some advantages, it's consistent with the recent improvements to type
variance and also with future ones. Also, it's hopefully not t
Voted "no" because of this paragraph:
> This RFC proposes to allow this, even if it has very few uses, and
because there is no reason to disallow a compatible redefinition.
I couldn't see a use-case.
In addition to that, this breaks the assumption that the topmost abstract
signature is the autho
Yes, yes you are :D Quick reminder:
```php
interface iA { function bar(stdClass $x); }
interface iB extends iA { function bar($x): stdClass; } // OK
class cA { function bar(stdClass $x) {} }
class cB extends cA { function bar($x): stdClass {} } /
