Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:101762 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 19605 invoked from network); 4 Feb 2018 21:00:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Feb 2018 21:00:28 -0000 Authentication-Results: pb1.pair.com header.from=kontakt@beberlei.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=kontakt@beberlei.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain beberlei.de from 209.85.215.53 cause and error) X-PHP-List-Original-Sender: kontakt@beberlei.de X-Host-Fingerprint: 209.85.215.53 mail-lf0-f53.google.com Received: from [209.85.215.53] ([209.85.215.53:33857] helo=mail-lf0-f53.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 55/F6-49805-A64777A5 for ; Sun, 04 Feb 2018 16:00:27 -0500 Received: by mail-lf0-f53.google.com with SMTP id k19so39038038lfj.1 for ; Sun, 04 Feb 2018 13:00:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=beberlei-de.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=sdDlMUjN801YzJyWlBK0v0oilCMMLaBGpG+VAByKCBk=; b=XfASmkWtGvQv2QZWUzYG7fGaP4FOxw/zkG0XBSP8iaszW/X+gAHx2mj0hMJTjOOcTY lwMdXTJRMJ787w15YCwYsoCWssnMHPif/UHBJpuYIXFjbvaiyDr3WftE95eGsQudyC5q Eb/7nvxaZyDW5Jfz0oKblOqdFUTXFl6jm0NukJNGFWKtTTl/6gWZchPsh5TnAJo/0Ly+ VL//fHo6nO1nIcP7qwt9o1KyB02R8n1JtXx9ZJET65Z8gHUoWaoKrTiSfpP3UVwqK4od pjs64nszlMeJaHpPfZtbzlhSCi77fp8uZum4Wz+nXe91/ffk6rgdLtnPdn6FseDYOD6p eigg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=sdDlMUjN801YzJyWlBK0v0oilCMMLaBGpG+VAByKCBk=; b=b8GMwRaB+3Pc2F9p9ZaYkLTL2hfAIY4UAB+mKoJN7yj5W2IjtfrB6JkHNkY9hrZBnp FhOA1dNxXztymS+AElAPZ03PHOjg6C+JnTvCTJoPoGw40BVmivAkwYIRG9uAsfGdwQq0 Rvi1cmDgYh5flgQNKeze03FKj11phy85vf/KEsuj40MEmckrnZG9Wa6xyzoKmYQInRmv MDSK2rS78iwe2DZgelxjWYTchr2TlRDEvWtPBtI6enqenVmbPSX+Lx2Ea5QbRyuC7Elf fMf8AHytQNkFXobJEH3x9t9th9eDEXva8PEoP4wkH1r2A/nRO3LBf9w7a4/I6zDzJsB5 wh+g== X-Gm-Message-State: AKwxytd5ZGWzru65m348ArHRmyd3AipMfpSxtZDJFJdTuLheJSJFQ6MK X+wUrvR0dEOBjc8BWYGF/lJa6twob7uxdUdYOf0JoA== X-Google-Smtp-Source: AH8x226/y08o79ZcocXSOQ+NTx/uj8eDYLSg4JJxqJ/w3/1Pa9/WUeJL1OX6kecBWV67rCcuLR/ApKZHBChxhhPmnIs= X-Received: by 10.25.165.145 with SMTP id o139mr29097642lfe.81.1517778022743; Sun, 04 Feb 2018 13:00:22 -0800 (PST) MIME-Version: 1.0 References: In-Reply-To: Date: Sun, 04 Feb 2018 21:00:12 +0000 Message-ID: To: Wes Cc: PHP Internals Content-Type: multipart/alternative; boundary="001a114118e2e4d5dc0564693b5f" Subject: Re: [PHP-DEV] [RFC][DISCUSSION] Deprecation of fallback to root scope From: kontakt@beberlei.de (Benjamin Eberlei) --001a114118e2e4d5dc0564693b5f Content-Type: text/plain; charset="UTF-8" On Sat, Feb 3, 2018 at 9:27 AM, Wes wrote: > Hello PHPeople. I just published the RFC "Deprecation of fallback to root > scope". > > It is quite a substantial change, but as you can read in the RFC, can be a > (basically) transparent one. > I'm referring to the possibility to shim it in userland. Essentially, this > would move the feature from core to userland. > > I hope you like it. Let me know what you think. > > https://wiki.php.net/rfc/fallback-to-root-scope-deprecation To get the same benefits (jit and such) wouldn't it be better to introduce a "use function root;" or similar statement or a declare() to specify this file imports all root functions? I am with stas that this will go towards a huge BC break if the deprecation was acted on at any time in the future. and in addition people will silence the notices on global error reporting level, because violations would happen on a massive scale, inclusing the cost of them being raised dragging performance down. This will be a problem since other notices will go unnoticed. --001a114118e2e4d5dc0564693b5f--