Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101753
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.52 as permitted sender)
MIME-Version: 1.0
Sender: morrison.levi@gmail.com
In-Reply-To: <CAOv67gupR-JFOB5XOudWnOf62RUtPXe-xESpnrGorAQMgQzJgQ@mail.gmail.com>
References: <CAOv67gvh_TM8B+ZvJeMwQDN7wnC+n7JiW78Ydk+V3wRjsXigBA@mail.gmail.com>
 <CADyq6sLmP4TF5KkStjYFSHDUc9e-md9WQVGzitxgb7vCADd7iQ@mail.gmail.com>
 <CANUQDChSjKfp=yWB5Fv=fgY=7oO5WmrkcMLvLWsAafHnXmbOwg@mail.gmail.com> <CAOv67gupR-JFOB5XOudWnOf62RUtPXe-xESpnrGorAQMgQzJgQ@mail.gmail.com>
Date: Sat, 3 Feb 2018 09:31:26 -0700
Message-ID: <CAFMT4NruyqR6LBdXH=nquyaW01daA-mSOPgtJEFDfYYBMPwyow@mail.gmail.com>
To: Wes <netmo.php@gmail.com>
Cc: Niklas Keller <me@kelunik.com>, Marco Pivetta <ocramius@gmail.com>, 
	PHP Internals <internals@lists.php.net>
Content-Type: text/plain; charset="UTF-8"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Deprecation of fallback to root scope
From: levim@php.net (Levi Morrison)

On Sat, Feb 3, 2018 at 3:22 AM, Wes <netmo.php@gmail.com> wrote:
> No idea, I'm not really sure what's the difference between E_STRICT and
> E_DEPRECATED.
> Yeah the shim is just a rough POC (completely forgot that define() can
> define in namespaces).
> Nicolas Grekas on twitter also suggested that we should introduce
> function_alias() that works like class_alias().
> With that the shim would be literally a couple of lines long.

From our manual:

> E_NOTICE : Run-time notices. Indicate that the script encountered something that could indicate an error, but could also happen in the normal course of running a script.
> E_DEPRECATED: Run-time notices. Enable this to receive warnings about code that will not work in future versions.
> E_STRICT: Enable to have PHP suggest changes to your code which will ensure the best interoperability and forward compatibility of your code.

In my opinion we should emit E_STRICT until we know when the feature
will be removed. At that point we can promote it to E_DEPRECATED and
specifically cite when it will be removed. In any case, E_NOTICE does
not seem appropriate.