[PHP-DEV] Re: VCS Account Request: nusphere

VCS Account Rejected: nusphere rejected by kalle /o\ -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: https://www.php.net/unsub.php

Re: [PHP-DEV] VCS Account Request: ondrejmirtes

Hi Den lør. 11. jul. 2020 kl. 08.43 skrev Ondřej Mirtes : > > The main reason is to be able to vote on PHP RFCs. I\ve created > PHPStan, a popular open-source static analyser. > > This submission is endorsed by Gabriel Caruso, a current release manager of > PHP 8. You do not need a VCS account

[PHP-DEV] VCS Account Request: ondrejmirtes

The main reason is to be able to vote on PHP RFCs. I\ve created PHPStan, a popular open-source static analyser. This submission is endorsed by Gabriel Caruso, a current release manager of PHP 8. -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit:

Re: [PHP-DEV] [VOTE] Named arguments

> Then the question becomes, do we rename parameters a lot? I doubt it's a > large problem, and even then the variadics support makes it very easy to > handle in a backwards compatible way. In addition libraries are always open > to declare they don't consider named parameters as part of their

Re: [PHP-DEV][RFC][VOTE] Rename T_PAAMAYIM_NEKUDOTAYIM to T_DOUBLE_COLON

Hello Internals The voting has closed with 44 for and 30 against. The RFC has not been accepted as it did not meet the 2/3 requirement to be approved, thank you to everyone for joining the discussions and turned out to vote. -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals -

Re: [PHP-DEV] Microsoft Support of PHP on Windows

Jan Ehrhardt in php.internals (Fri, 10 Jul 2020 18:52:06 +0200): >? Good Guy ? in php.windows (Fri, 10 Jul 2020 17:39:54 +0100): >>On 10/07/2020 17:09, Trevor Holyoak via php-windows wrote: >>> What does this mean? PHP 8 and forward will not be available for >>> Windows? Or is just won't be

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On 10/07/2020 09:54, Nikita Popov wrote: For me, dealing with PHP <-> PECL moves is an important part of adopting namespaces in php-src, and I don't think the current proposal addresses this issue sufficiently. (One way to address it would be to drop the PHP\ prefix, and use unvendored namespace

Re: [PHP-DEV] Re: Microsoft Support of PHP on Windows

Chase Peeler in php.internals (Fri, 10 Jul 2020 12:43:00 -0400): >My other fear is that if official support for windows is dropped, PHP >itself will no longer be developed with windows in mind. One reason >building it is pretty easy is because it was developed to be built on >Windows. If that

Re: [PHP-DEV] Microsoft Support of PHP on Windows

? Good Guy ? in php.windows (Fri, 10 Jul 2020 17:39:54 +0100): >On 10/07/2020 17:09, Trevor Holyoak via php-windows wrote: >> What does this mean? PHP 8 and forward will not be available for >> Windows? Or is just won't be supported by Microsoft? >> >> >It's means that Microsoft won't be spending

Re: [PHP-DEV] Re: Microsoft Support of PHP on Windows

On Fri, Jul 10, 2020 at 12:32 PM Jan Ehrhardt wrote: > ? Good Guy ? in php.internals (Fri, 10 Jul 2020 17:16:07 +0100): > >On 10/07/2020 17:01, Jan Ehrhardt wrote: > >> I am building PHP for Windows myself, but I know from the questions I am > >> getting that a lot of corporate customers of

Re: [PHP-DEV] Re: Microsoft Support of PHP on Windows

? Good Guy ? in php.internals (Fri, 10 Jul 2020 17:16:07 +0100): >On 10/07/2020 17:01, Jan Ehrhardt wrote: >> I am building PHP for Windows myself, but I know from the questions I am >> getting that a lot of corporate customers of Microsoft are running PHP >> on Windows Server 2016 or 2019. They

Re: [PHP-DEV] Re: Microsoft Support of PHP on Windows

On 10/07/2020 17:01, Jan Ehrhardt wrote: I am building PHP for Windows myself, but I know from the questions I am getting that a lot of corporate customers of Microsoft are running PHP on Windows Server 2016 or 2019. They are only allowed to use the official binaries that are supplied on

[PHP-DEV] Re: Microsoft Support of PHP on Windows

Hi Dale, "Dale Hirt via internals" in php.internals (Thu, 9 Jul 2020 18:48:44 +): >My name is Dale Hirt and I am the project manager for PHP inside >Microsoft. > >We currently support PHP with development and build efforts for PHP 7.3, >and PHP 7.4. In addition, we help with building PHP 7.2

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Instance as boolean

>>> >>> Frankly this is something subject to personal opinions and will change >>> over time according to community shifts. >>> >> >> Not sure what's "subject to personal opinions" in the objective bug exposed >> in the snippet above? >> > > So there is a bug in a contrived code snippet

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, Jul 10, 2020 at 11:21 AM Marco Pivetta wrote: > Hi Nikita, > > I kept my "NO" stance here, as per discussion in > https://externals.io/message/110004#110005, where I provided (in my > opinion) good/safe alternatives to arrays as input parameters. > > The BC implications on this RFC

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On Thu, 9 Jul 2020 at 18:04, Larry Garfield wrote: > > I've no idea what the rules are around new version numbers > of RFCs that haven't been up for a vote yet. I pretty strongly recommend people against re-using documents. If it's going to change significantly, using a new doc makes it easier

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On Fri, Jul 10, 2020, at 3:54 AM, Nikita Popov wrote: > On Tue, Jul 7, 2020 at 4:47 PM Larry Garfield > wrote: > > > On Tue, Jun 23, 2020, at 7:30 PM, Larry Garfield wrote: > > > Greetings, Internalians. > > > > > > There has been much talk of the \PHP namespace of late, including one > > >

Re: [PHP-DEV][RFC] Saner numeric strings

Good afternoon Internals, I rewrote the RFC to improve clarity but the content is mostly identical with one small change is that the warning change from 'Illegal offset type' to 'String cast occurred' for string offsets such as '5.5' will be a secondary implementation vote as it adds some

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, 10 Jul 2020 at 11:24, Marco Pivetta wrote: > If "array" is all you have to pass on as input, `fromArray` is what you > can certainly use: that's useful when de-serializing from JSON input, DB, > serialized state, etc. > > It certainly isn't meant to pass in the array via hand-crafted

Re: [PHP-DEV] [VOTE] Named arguments

Hey Rowan, On Fri, Jul 10, 2020 at 12:11 PM Rowan Tommins wrote: > On Fri, 10 Jul 2020 at 10:21, Marco Pivetta wrote: > > > I kept my "NO" stance here, as per discussion in > > https://externals.io/message/110004#110005, where I provided (in my > > opinion)

Re: [PHP-DEV] [VOTE] Named arguments

On Fri, 10 Jul 2020 at 10:21, Marco Pivetta wrote: > I kept my "NO" stance here, as per discussion in > https://externals.io/message/110004#110005, where I provided (in my > opinion) good/safe alternatives to arrays as input parameters. > For the record, I maintain my reaction from

Re: [PHP-DEV] [VOTE] Named arguments

Hi Nikita, I kept my "NO" stance here, as per discussion in https://externals.io/message/110004#110005, where I provided (in my opinion) good/safe alternatives to arrays as input parameters. The BC implications on this RFC still largely outweigh any advantages that it brings, from my

Re: [PHP-DEV] [RFC] \PHP namespace usage heuristics

On Tue, Jul 7, 2020 at 4:47 PM Larry Garfield wrote: > On Tue, Jun 23, 2020, at 7:30 PM, Larry Garfield wrote: > > Greetings, Internalians. > > > > There has been much talk of the \PHP namespace of late, including one > > unsuccessful RFC. In the discussion, the pushback broke down into two > >

[PHP-DEV] [VOTE] Named arguments

Hi internals, I have opened voting on the named arguments RFC: https://wiki.php.net/rfc/named_params Voting will close on 2020-07-24. Regards, Nikita