Hi,
The PHP development team announces the immediate availability of PHP
7.2.23. This is a bugifx release.
For source downloads of PHP 7.2.23 please visit our downloads page.
Windows binaries can be found on the PHP for Windows site.
The list of changes is recorded in the ChangeLog.
Release
On Thu, Sep 26, 2019 at 4:31 AM Christian Schneider
wrote:
> Am 26.09.2019 um 09:41 schrieb Nikita Popov :
> > * Remainder: 54 yes, 3 no. Accepted with 95% majority.
>
> Just for the record:
> The one I'm most concerned about here is the foreach on undefined
> variables throwing an exception.
>
On Thu, 26 Sep 2019 at 10:48, Peter Cowburn wrote:
> I just want to go on the record in saying that I am very, very disappointed
> that a choice that only got 28% of the overall votes, and only 33% of votes
> in the "we want change" scenario, is being taken as the will of the
> overwhelming
> While certainly not the primary reason for why we should support union
types, the reason why I brought this proposal forward at this time
specifically, is that the lack of union types is a blocker for my pet
project of providing comprehensive type annotations for internal functions.
Supporting
The PHP development team announces the immediate availability of PHP
7.3.10. This is a security release which also contains several bug fixes.
All PHP 7.3 users are encouraged to upgrade to this version.
For source downloads of PHP 7.3.10 please visit our downloads page.
Windows binaries can be
> Confirming that most spam got nicely reduced now. Thank you for
> enabling spam filters. There are now only few of those spam mails
> passing through but I guess reading one or two messages with pharmacy
> and similar content can be ignored and deleted on the mods side.
Thanks for the feedback.
Hello,
On Thu, 5 Sep 2019 at 03:45, Sascha Schumann
wrote:
>
> Looking good (test 3).
>
> Please alert syst...@php.net if you have issues sending emails to
> *@lists.php.net.
>
> Sascha
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit:
On 26.09.2019 at 10:06, Nikita Popov wrote:
> This RFC is currently held up by a lack of implementation. Once that is
> done, the RFC will go forward as-is (barring any novel concerns). Because I
> consider it an important part of the overall proposal (*), I will neither
> remove the false type,
> Le 26 sept. 2019 à 11:21, Lynn a écrit :
>
>
> I'm not sure this type should be declarable in user-land, meaning it's
> limited to the core and a marker for legacy.
In general, we should avoid to give builtin code functionality that can’t be
reproduced in userland, unless there is a good
On Thu, 26 Sep 2019 at 08:42, Nikita Popov wrote:
> On Thu, Sep 12, 2019 at 2:17 PM Nikita Popov wrote:
>
> > Hi internals,
> >
> > I've opened the vote on //wiki.php.net/rfc/engine_warnings.
> >
> > There are 4 votes, all of them independent. The first 3 are for specific
> > cases that were
On Thu, Sep 26, 2019 at 10:06 AM Nikita Popov wrote:
>
> This RFC is currently held up by a lack of implementation. Once that is
> done, the RFC will go forward as-is (barring any novel concerns). Because I
> consider it an important part of the overall proposal (*), I will neither
> remove the
Am 26.09.2019 um 09:41 schrieb Nikita Popov :
> * Remainder: 54 yes, 3 no. Accepted with 95% majority.
Just for the record:
The one I'm most concerned about here is the foreach on undefined variables
throwing an exception.
While this was already promoted to a warning at an earlier stage it still
On Tue, Sep 24, 2019 at 10:06 PM Sara Golemon wrote:
> On Tue, Sep 24, 2019 at 12:24 PM Claude Pache
> wrote:
> > The choice of supporting precisely the two literal values `null` and
> `false`
> > is not arbitrary: They are the two values that are the most often used as
> > sentinel values (for
> I would tend to agree with Sara. That seems to be the only issue of
contention and it is (AFAIK) reasonably straightforward to add "later"
without blocking the rest of Union types. It would mean some functions
wouldn't be able to get a fully accurate return type yet but... they've
survived
On Thu, Sep 12, 2019 at 2:17 PM Nikita Popov wrote:
> Hi internals,
>
> I've opened the vote on //wiki.php.net/rfc/engine_warnings.
>
> There are 4 votes, all of them independent. The first 3 are for specific
> cases that were controversial during the discussion, the last one is for
> the
15 matches
Mail list logo
