Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102452
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.128.182 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAESVnVrJo8BH=gMf07qq9MsgT6ziqWJO6JPgxVgVuStr+-5cpw@mail.gmail.com>
References: <CAF+90c_+GZNrV1SC9q=Y3C=L3LMnoXX7J3zK6=kS9-sMXHZZow@mail.gmail.com>
 <CAESVnVrJo8BH=gMf07qq9MsgT6ziqWJO6JPgxVgVuStr+-5cpw@mail.gmail.com>
Date: Tue, 26 Jun 2018 13:27:42 +0200
Message-ID: <CADyq6s+ETj=E0zNyTFkUknr6ipSf75NcBYoYS3KgeO=vU2W5JQ@mail.gmail.com>
To: Sara Golemon <pollita@php.net>
Cc: Nikita Popov <nikita.ppv@gmail.com>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000089acfa056f89ca6a"
Subject: Re: [PHP-DEV] [RFC] Deprecations for PHP 7.3
From: ocramius@gmail.com (Marco Pivetta)

--00000000000089acfa056f89ca6a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 25, 2018 at 9:32 PM, Sara Golemon <pollita@php.net> wrote:

> > Defining a free-standing assert() function
> >
> Eww, yeah. I can see that problem.  I'm not a huge fan of banning all
> namespaced assert() function declarations, but it's certainly the most
> direct "solution" to the problem.  A very quick scan of github only
> shows one effected usage in a repo with no followers/stars apart from
> the owner.  Given the lack of whole-program analysis, it's either ban
> the declarations, or abandon elision.  Frankly, the number of people
> taking advantage of the free dev-only check is probably way higher
> than the number trying to define a function called 'assert' so.... =F0=9F=
=98=AC


Or require a FQN for an imported `assert()`? Importing functions is getting
traction.

Marco Pivetta

http://twitter.com/Ocramius

http://ocramius.github.com/

--00000000000089acfa056f89ca6a--