Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:101780
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 74.125.82.44 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAFMT4Nqz6Tdr3cGvoU2_k_dTRNcTiuqL--mkA26LeGwCjb6=tw@mail.gmail.com>
References: <CAOv67gvh_TM8B+ZvJeMwQDN7wnC+n7JiW78Ydk+V3wRjsXigBA@mail.gmail.com>
 <CAEPJdunk-uWhaqOtUP24qNzqv-EBvJnJncikPsfLBtjPkfwH8g@mail.gmail.com>
 <07d9e3a0-d516-aa77-4818-ce8b02e8dd08@gmail.com> <CAEPJdu=SBAJiPf-jP27ViQJ=Rk4fk5m841L8=LhBa9HtScdSPA@mail.gmail.com>
 <CAFMT4Nqz6Tdr3cGvoU2_k_dTRNcTiuqL--mkA26LeGwCjb6=tw@mail.gmail.com>
Date: Tue, 6 Feb 2018 10:08:03 +0000
Message-ID: <CALKiJKqYGT6ZjtOORVvE7HpQJgs2n-Gx1h3L_D=r8JYTkzu=+w@mail.gmail.com>
To: PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="94eb2c1af74aba3b420564885a38"
Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Deprecation of fallback to root scope
From: rowan.collins@gmail.com (Rowan Collins)

--94eb2c1af74aba3b420564885a38
Content-Type: text/plain; charset="UTF-8"

On 6 February 2018 at 01:51, Levi Morrison <levim@php.net> wrote:

> It's fine to ignore them as long as they fix them later. That's
> precisely why I think E_STRICT is a good category for these notices.
> If, however, they ignore them forever that's their fault; we are
> simply providing advanced notice of a behavior we'd like to eventually
> change.
>
> Let me put "eventually" into perspective. We will probably have a 7.3
> before we have an 8.0. This means that 8.0, the absolute earliest
> version we could remove this feature, is at least 2 years away before
> it reaches *any* of our users. Unless we extend it like we did with
> the last 5.X release (and I think we probably should extend it) this
> means that users can run their existing code on an officially
> supported PHP 7 release for the next 4 years at the minimum. I am
> fairly confident that for one reason or another it will delay another
> year or two, putting it at 5-6 years.
>


I think for a lot of people the "forever" in your first paragraph and the
"5-6 years" in your second paragraph will feel like the same thing. If the
message is "this might be removed some time in the next decade", people
will simply shrug and ignore it until an actual removal is announced;
thinking as a cynical user, there's no guarantee the recommendation won't
be changed back in future - we've had features "undeprecated" before.

As others have pointed out, even if you run an analyser over your own code
base to add \ in the appropriate places, you can't turn on E_STRICT notices
without being flooded until all your dependencies have done the same - and
there's no compelling reason for them to do so.

That's why I think having some concrete benefit much sooner is the only way
to stop people resenting this change. Build function autoloading in a way
that it only works if you opt out of the fallback, and *then* deprecate the
fallback mode, and it feels like progress rather than disruptive tinkering.

Regards,
-- 
Rowan Collins
[IMSoP]

--94eb2c1af74aba3b420564885a38--