[PHP-DEV] How to indicate support for unimplemented part of an RFC

Hi, What is the proper way to express support for an item that's not an official part of an RFC but is listed as an idea for future consideration? Specifically I wanted to give my "+1" for covariant return types which are mentioned in passing in this RFC: https://wiki.php.net/rfc/return_types.

[PHP-DEV] pcntl_signal & sa_siginfo

Hi All, Long-time lurker, first time questioner here. I'm currently working on a project wherein I end up forking off many subprocesses, but am trying to keep tabs on the progress of individual forks by having the children send a signal back up to their parent every so often. pcntl_socket, allow

Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable?

On 6/13/2016 4:32 PM, Joe Watkins wrote: > You can count the number of people putting in the majority of this effort > on your fingers ... erecting a road block in front of them in the name of > unobtainable BC is harmful to the apparent goals of the project at this > time. > The work of these pe

Re: [PHP-DEV] [RFC] [VOTE] Fix inconsistent behavior of $this variable

On 6/13/2016 12:48 PM, Pascal MARTIN, AFUP wrote: > Hi, > > At AFUP, we agree the inconsistency outlined in this RFC is quite > strange and fixing it would be nice for the language. > > But, we are not sure this should be done in PHP 7.1 (or any other minor > version, actually). > > Instead, som

Re: [PHP-DEV] Re: [RFC] Iterable

On 6/13/2016 5:59 PM, Levi Morrison wrote: > My opinion is contrary: the union type is the cleaner solution as it > does not require special casing machinery in the engine. > I am a huge fan of the union types but this is such a common requirement that it requires a pseudo compound type in my opi

Re: [PHP-DEV] Re: [RFC] Iterable

On 13.06.2016 at 17:59, Levi Morrison wrote: > On Mon, Jun 13, 2016 at 5:42 AM, Christoph Becker wrote: >> On 11.06.2016 at 01:37, Aaron Piotrowski wrote: >>> I would like to propose a new iterable pseudo-type that accepts both arrays >>> and objects implementing Traversable. Values accepted by

Re: [PHP-DEV] Re: [RFC] Iterable

On Mon, Jun 13, 2016 at 5:42 AM, Christoph Becker wrote: > On 11.06.2016 at 01:37, Aaron Piotrowski wrote: >> I would like to propose a new iterable pseudo-type that accepts both arrays >> and objects implementing Traversable. Values accepted by iterable can then >> be used with foreach and yiel

Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable?

On Mon, Jun 13, 2016 at 4:32 PM, Joe Watkins wrote: > Afternoon internals, > > > Is there a roadmap somewhere that describes this, or any background > discussion of doing this within the 7.x series, rather than planning for > 8.0? > > We have no such sensible thing as a plan :) > > The reason for

Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable?

Afternoon internals, > Is there a roadmap somewhere that describes this, or any background discussion of doing this within the 7.x series, rather than planning for 8.0? We have no such sensible thing as a plan :) The reason for the existence of PHP 7 (ng) is efficiency of the kind I described, t

Re: [PHP-DEV] [RFC] [VOTE] Replace "Missing argument" warning with "Too few arguments" exception

On Mon, Jun 13, 2016 at 9:07 AM, Rowan Collins wrote: > On 06/06/2016 08:22, Dmitry Stogov wrote: > >> >> This mini RFC has been moved to "Voting" state. Voting >> began on Jun 6 and will close on June 16. >> >> You can find the full RFC at: https://wiki.php.net/rfc/too_few_args >> >> > The more

Re: [PHP-DEV] [RFC] [VOTE] Replace "Missing argument" warning with "Too few arguments" exception

Le lun. 6 juin 2016 à 09:23, Dmitry Stogov a écrit : > Hi, > > > This mini RFC has been moved to "Voting" state. Voting > began on Jun 6 and will close on June 16. > > You can find the full RFC at: https://wiki.php.net/rfc/too_few_args > > I encourage everyone to read the RFC and cast your vote

Re: [PHP-DEV] [RFC] [VOTE] Replace "Missing argument" warning with "Too few arguments" exception

On 06/06/2016 08:22, Dmitry Stogov wrote: Hi, This mini RFC has been moved to "Voting" state. Voting began on Jun 6 and will close on June 16. You can find the full RFC at: https://wiki.php.net/rfc/too_few_args Hi, The more I think about this RFC, the less I agree with it being included

Re: [PHP-DEV] [RFC] [PRE-VOTE] Union types

On 04.06.2016 at 16:37, Bob Weinand wrote: >> Am 4.6.2016 um 16:17 schrieb Christoph Becker : >> >> On 04.06.2016 at 14:15, Bob Weinand wrote: >> Am 04.06.2016 um 13:45 schrieb Niklas Keller : For Aerys\Host it could also be solved with an interface that just doesn't have any

Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable?

On 13/06/2016 10:35, Joe Watkins wrote: Backward compatibility is important. Also important is the long term goals for PHP, or at least for this major version of PHP: The goal is to make Zend so efficient that generating machine code from user code becomes a deployable solution. OK, that's

[PHP-DEV] Re: Request for Karma

On 11.06.2016 at 17:19, Fleshgrinder wrote: > I would like to request Karma for the Wiki. > > I would like to write RFCs for the features that I develop and help > others with their RFCs. > > My Wiki username is "fleshgrinder". Ping. IMO it's a no-brainer to grant Wiki karma to Richard. -- C

[PHP-DEV] Re: [RFC] Iterable

On 11.06.2016 at 01:37, Aaron Piotrowski wrote: > I would like to propose a new iterable pseudo-type that accepts both arrays > and objects implementing Traversable. Values accepted by iterable can then be > used with foreach and yield from, or help to reduce type-checking logic in > general. >

Re: [PHP-DEV] [RFC] Throw Exception on Attempt of ConstantRedefinition

On 11.06.2016 at 17:01, Fleshgrinder wrote: > On 6/10/2016 10:06 PM, Dmitry Stogov wrote: >> >> Please review: https://wiki.php.net/rfc/constant_redefinition > > This would be a breaking change in a minor release again. > > -1 > > However +1 for PHP 8. I'm also somewhat concerned with regard t

[PHP-DEV] NEUTRAL Benchmark Results for PHP Master 2016-06-13

Results for project PHP master, build date 2016-06-13 06:29:02+03:00 commit: e933da9 previous commit:33f6fc1 revision date: 2016-06-12 18:40:24+01:00 environment:Haswell-EP cpu:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz 2x18 cores, stepping 2, LLC 45 MB

Re: [PHP-DEV] [RFC] [VOTE] Fix inconsistent behavior of $this variable

Le 06/06/2016 09:18, Dmitry Stogov a écrit : You can find the full RFC at: https://wiki.php.net/rfc/this_var I encourage everyone to read the RFC and cast your vote towards whichever option you feel is the best for the language and the community. Hi, At AFUP, we agre

Re: [PHP-DEV] [RFC][Vote] Typed Properties

Morning, > This wouldn't affect the performance of untyped properties at all. There are extra instructions in that code. When the code you have is only 5 instructions, adding 1 more instruction makes a 20% increase in instructions ... That is what we are looking at in these micro benchmarks; Th

Re: [PHP-DEV] Is the "No BC Breaks in Minor Releases" policy enforceable?

Morning internals, As already explained, strictly following SemVer is not possible for a project the size of PHP, with a release process such as PHP has. Backward compatibility is important. Also important is the long term goals for PHP, or at least for this major version of PHP: The goal