Re: [PHP-DEV] Drop warning about non-public magic methods

Hi Grabriel, Hello internals, > > During the development of https://wiki.php.net/rfc/magic-methods-signature > I > found something that I'd like to share with you, and possibly propose to > drop it: there's a warning that php-src throws when a magic method is > declared with visibility different

[PHP-DEV] RE: [EXTERNAL] Re: [PHP-DEV] Microsoft Statement on PHP

We simply followed this guide: https://wiki.php.net/internals/windows/stepbystepbuild_sdk_2 -Original Message- From:  Good Guy  Sent: Monday, July 13, 2020 6:14 PM To: internals@lists.php.net Subject: [EXTERNAL] Re: [PHP-DEV] Microsoft Statement on PHP On 14/07/2020 00:46, Dale

Re: [PHP-DEV] Microsoft Statement on PHP

On 14/07/2020 00:46, Dale Hirt via internals wrote: For over a decade, Microsoft has helped fund build infrastructure for the PHP for Windows community. We decided to transition out of this effort starting with the upcoming release and as part of our yearly review of this investment. During

[PHP-DEV] RE: [EXTERNAL] [PHP-DEV] Re: Microsoft Statement on PHP

There is no policy change. This is a clarification of the original email. --Dale -Original Message- From: Mark Randall Sent: Monday, July 13, 2020 4:52 PM To: internals@lists.php.net Subject: [EXTERNAL] [PHP-DEV] Re: Microsoft Statement on PHP On 14/07/2020 00:46, Dale Hirt via

[PHP-DEV] Re: Microsoft Statement on PHP

On 14/07/2020 00:46, Dale Hirt via internals wrote: While we will no longer work on PHP builds for Windows, expect to see us remain involved in PHP in many ways across MS as we continue supporting PHP developers and collaborating with the community on security fixes. I admit to a certain

[PHP-DEV] Microsoft Statement on PHP

For over a decade, Microsoft has helped fund build infrastructure for the PHP for Windows community. We decided to transition out of this effort starting with the upcoming release and as part of our yearly review of this investment. During this transition, we will work with members of the

Re: [PHP-DEV] [RFC][DISCUSSION] Language Constructs Syntax Changes

On 05-07-2020 09:35, Michał Marcin Brzuchalski wrote: > The proposal is to allow two statements to skip parentheses so they don't > look like expressions. I like small improvements like this one. They may not look like much but they do add up to arrive at a cleaner language in the long run.

Re: [PHP-DEV] Possible RFC: UniqueInterface that throws exception at refcount > 1

2020-07-11 23:24 GMT, Rowan Tommins : > On 11 July 2020 22:47:21 BST, "Olle Härstedt" > wrote: >>You're misunderstanding. :) Yes, it should be shared, but not with the >>same access level as the owner. If a dependent class closes the >>connection it will cause spooky-action-at-a-distance

Re: [PHP-DEV] Drop warning about non-public magic methods

On 13/07/2020 19:32, Gabriel Caruso wrote: This warning does not make much sense as the magic method is executed regardless of its visibility. Should it be dropped? This seems to be the bigger issue... if something is specified as private, nothing outside its scope has any rights to access it,

Re: [PHP-DEV] Drop warning about non-public magic methods

Curious. I tend to follow PSR-12 (with few exceptions): https://www.php-fig.org/psr/psr-12/#44-methods-and-functions Which requires visibility declaration on all members (methods and properties). Would dropping the requirement

[PHP-DEV] Drop warning about non-public magic methods

Hello internals, During the development of https://wiki.php.net/rfc/magic-methods-signature I found something that I'd like to share with you, and possibly propose to drop it: there's a warning that php-src throws when a magic method is declared with visibility different than `public`:

Re: [PHP-DEV] Changing default assertion mode to throw exceptions

Hi! > > Hello everyone, > > I'd like to change the default mode of assertion failures to throw. > The current default is to warn. In my opinion this is a bad strategy: > the engine asserted that something that is expected to be true is not, > so executing further is a bad idea. This leaves

[PHP-DEV] Changing default assertion mode to throw exceptions

Hello everyone, I'd like to change the default mode of assertion failures to throw. The current default is to warn. In my opinion this is a bad strategy: the engine asserted that something that is expected to be true is not, so executing further is a bad idea. This leaves throwing or bailing out.

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Allow objects to declareemptiness and by extension truthiness

On 13.07.2020 at 17:18, Josh Bruce wrote: > Re the wiki: I can edit pages now, it doesn’t look like I can create them. > There’s another thread I’ve been watching and I think I need more karma to > make that a thing. I will continue working on this and if it generates enough > pull then maybe

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Allow objects to declare emptiness and by extension truthiness

On Mon, Jul 13, 2020 at 5:33 PM Josh Bruce wrote: > > >> Latest version as we zero in on what this is really about: >> https://bit.ly/php-0002 >> >> I have a really hard time understanding what is actually being proposed > here. You mention the introduction of the

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Allow objects to declare emptiness and by extension truthiness

> > Latest version as we zero in on what this is really about: > https://bit.ly/php-0002 > > > I have a really hard time understanding what is actually being proposed here. > You mention the introduction of the

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Allow objects to declare emptiness and by extension truthiness

>> Latest version as we zero in on what this is really about: >> https://bit.ly/php-0002 >> > 1) The 2 places that you have lists of "this thing produces true/false" could > likely stand to be turned into tables to make it clearer, especially when > demonstrating

Re: [PHP-DEV] [RFC][DISCUSSION] Language Constructs Syntax Changes

Hey Michał, Personally, I think instead of making `declare(strict_types=1);` to look more like a constant, we should make it look more like a function. Since it seems that the named parameters RFC is going to be accepted, I think allowing for alternative `declare(strict_types: 1);` syntax would

Re: [PHP-DEV] [RFC][DISCUSSION] Language Constructs Syntax Changes

Hi Nikita, pon., 13 lip 2020 o 12:41 Nikita Popov napisał(a): > On Sun, Jul 5, 2020 at 9:36 AM Michał Marcin Brzuchalski < > michal.brzuchal...@gmail.com> wrote: > >> Hi internals, >> >> I realise we're tight to the deadline but from my calculations, >> this RFC should fit with 2w discussion

Re: [PHP-DEV] [RFC][DISCUSSION] Language Constructs Syntax Changes

On Sun, Jul 5, 2020 at 9:36 AM Michał Marcin Brzuchalski < michal.brzuchal...@gmail.com> wrote: > Hi internals, > > I realise we're tight to the deadline but from my calculations, > this RFC should fit with 2w discussion and 2w voting before feature freeze. > > The proposal is to allow two

Re: [PHP-DEV] [CONCEPT][DISCUSSION] Allow objects to declare emptiness and by extension truthiness

On Sun, Jul 12, 2020 at 7:49 PM Josh Bruce wrote: > Latest version as we zero in on what this is really about: > https://bit.ly/php-0002 > > Other threads: > > 1. https://externals.io/message/110879 < > https://externals.io/message/110879> > 2.