Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:98048 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 21180 invoked from network); 30 Jan 2017 19:06:44 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 30 Jan 2017 19:06:44 -0000 Authentication-Results: pb1.pair.com smtp.mail=morrison.levi@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=morrison.levi@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.215.50 as permitted sender) X-PHP-List-Original-Sender: morrison.levi@gmail.com X-Host-Fingerprint: 209.85.215.50 mail-lf0-f50.google.com Received: from [209.85.215.50] ([209.85.215.50:33520] helo=mail-lf0-f50.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 1E/99-51557-1CE8F885 for ; Mon, 30 Jan 2017 14:06:41 -0500 Received: by mail-lf0-f50.google.com with SMTP id x1so112924855lff.0 for ; Mon, 30 Jan 2017 11:06:40 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=lVwZ9ZhW4cJoMPSKXCWFdP+FMDpZob+9HfWvwic+tY4=; b=KIdWmoarPP8saAgPaLtDZMzYb2mxOaT/tJIAaXrzoLCEQoRN3PqpK6xYloCu9pBlRL tC/1lvs1DL//lZdPgQY5S9WcPh0wLNrsb0/aF/6e44ViMdHNNztq8Wancd725qqaAP+J kIC8uamuKUI3fyzhoA8LqmwKKKURSNm1qQxc/jotsAaQL/2XmSmuv8Gtl7dveywAG4Vr 9PWh89a7TN1H3J0Wg0tqR00HEVXUt4E+f9y648RSXM/rtKPYpWUj/8gXnJ19UttOZHyy ICn5jwYvGuzw/ArtHy3s4J1rL7lzhEvWfizf+5S4KxLgsaPdYtFaw9D2QoAFb9GtD9iy medQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=lVwZ9ZhW4cJoMPSKXCWFdP+FMDpZob+9HfWvwic+tY4=; b=QSsbjkZ4P5aiCATzDPbxxt58orxhchz4wHIlYc++rcPJz7cnWpdi7FDXEEQmPtzkmu iBqHevDi6hBkhBv5hAS7HVmfjCMzFjGxWFpmbJX7uqj+3hu+1/drMVw28nD8+bzMmDj3 T2dVB8Da2vm7m7rXrQ3CqUazuaska8QNbB6KXJcmAXpa55Vn9kiIsBChO5mUCffeMLyk ArOT6GQBzHcJFxStg+ekdOY+nbG49RC9VGGpiXgP5iFWWbkB5/ZpAT9Dh2TmYFZaXIJ/ g0ypjYNIU5mzBAqRrweeRaIiRua+9g3VQeV0wMLvzjTTYTwiw2JtPZxrtDZpBFTACMgo rgag== X-Gm-Message-State: AIkVDXK5kgOFomZEg002MuKuTwq24mXQIkKV+UpPKe4hzC6tW9+x4AOlFs7vEqg3USQOeqrocwmvxkEOZ0ddiw== X-Received: by 10.25.34.196 with SMTP id i187mr7816540lfi.176.1485803198183; Mon, 30 Jan 2017 11:06:38 -0800 (PST) MIME-Version: 1.0 Sender: morrison.levi@gmail.com Received: by 10.25.151.139 with HTTP; Mon, 30 Jan 2017 11:06:37 -0800 (PST) In-Reply-To: References: <0c5fc86b-5050-fe73-7afa-b3e5a38ad370@gmail.com> Date: Mon, 30 Jan 2017 12:06:37 -0700 X-Google-Sender-Auth: 4qVHHDnQ7gWW9L1kdDxDo8sJylQ Message-ID: To: Nikita Popov Cc: Rowan Collins , PHP Internals Content-Type: text/plain; charset=UTF-8 Subject: Re: [PHP-DEV] [RFC] Deprecate and Remove Bareword (Unquoted) Strings From: levim@php.net (Levi Morrison) On Sun, Jan 29, 2017 at 1:50 PM, Nikita Popov wrote: > On Sun, Jan 29, 2017 at 8:33 PM, Rowan Collins > wrote: > >> Good evening all! >> >> Currently, if the constant FROB_ACTIVE is not defined, the code "echo >> FROB_ACTIVE;" results in an E_NOTICE and the string 'FROB_ACTIVE' being >> displayed. I would like to propose that this be changed to an E_WARNING in >> PHP 7.2, and to an Error in PHP 8.0. >> >> My reasoning for this includes: >> >> - consistency with other "undefined" errors, including the otherwise >> identical "echo \FROB_ACTIVE;" >> - the fallback to string appears to be largely undocumented except to >> discourage its use >> - the error can mask serious bugs, such as when mis-typing keywords >> >> I have tried to anticipate some of the questions that will be raised, so >> have drafted an RFC rather than trying to fit all the detail into one >> e-mail: https://wiki.php.net/rfc/deprecate-bareword-strings >> >> Please read my proposal, and let me know your thoughts. I have placed the >> RFC "under discussion", but will be happy to modify it based on feedback, >> and am in no haste to put it to a vote. >> > > Fully agree with this proposal. > > Also agree with the choice of throwing a Warning instead of a Deprecation. > Throwing a Deprecation would essentially *downgrade* the current error > level, which does not appear to be prudent. > > Nikita I also agree with the choice of throwing a Warning instead of a Deprecation. I'll be happy to see this feature removed. Good riddance!