Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:106929 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 91508 invoked from network); 11 Sep 2019 00:29:16 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 11 Sep 2019 00:29:16 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id 981B52D1F98 for ; Tue, 10 Sep 2019 15:04:44 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp3.php.net X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3301 81.224.0.0/12 X-Spam-Virus: No Received: from v-smtpout3.han.skanova.net (v-smtpout3.han.skanova.net [81.236.60.156]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by php-smtp3.php.net (Postfix) with ESMTPS for ; Tue, 10 Sep 2019 15:04:43 -0700 (PDT) Received: from [192.168.7.5] ([213.64.245.126]) by cmsmtp with ESMTPA id 7oFdihl6wXLfm7oFdivKEC; Wed, 11 Sep 2019 00:04:41 +0200 To: Nikita Popov References: Cc: PHP internals Message-ID: <55792af5-ff8c-ba35-5108-316ff3bc8fa8@telia.com> Date: Wed, 11 Sep 2019 00:04:43 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-GB X-CMAE-Envelope: MS4wfOkKsaiZ62T3h/ZZm9Xw6n6AUNXwQHYY/wvYwqZVdoY6fb3Nalz/gG+2qXqxIz/d8Ch4JHVcOJYlsca0iPCa9fixBnOQBNSWUlZJL++QDkvNu+G33dZR yEaIZkctdnZ8sLT14zigRmwo6LhPHhL1pyP3RurPThplNsjh9VkjHfrr55J5ITmVp4N/3KzfXkC7DAb6UpYsKahXzrmAFJ0qfPx4JAjaugMgXbBCntjnI58t X-Envelope-From: Subject: Re: [PHP-DEV] Re: [RFC] Reclassifying engine warnings From: bjorn.x.larsson@telia.com (=?UTF-8?Q?Bj=c3=b6rn_Larsson?=) Den 2019-09-10 kl. 15:31, skrev Nikita Popov: > On Wed, Aug 28, 2019 at 11:33 AM Nikita Popov wrote: > >> Hi internals, >> >> I think it's time to take a look at our existing warnings & notices in the >> engine, and think about whether their current classification is still >> appropriate. Error conditions like "undefined variable" only generating a >> notice is really quite mind-boggling. >> >> I've prepared an RFC with some suggested classifications, though there's >> room for bikeshedding here... >> >> https://wiki.php.net/rfc/engine_warnings >> >> Regards, >> Nikita >> > Heads up: This RFC may go to vote tomorrow. > > Nikita Hi, I recall an issue brought up about treatment of logfiles in production environment where PHP warning messages show up. Now, this RFC reclassifies some notices to warnings and some warnings to errors. Now suppose one have as a strategy to correct warnings & errors in logfiles, given that this RFC will lead to new items showing up in logfiles. Is it then worth mentioning in the RFC how this will affect handling to correct warnings & errors in logfiles? E.g. face the changes and fix  it or write some clever error handler to manage it or just try to suppress the new items. Anyway, I'm in favour of this RFC since it gives a more consistent classification of notices, warnings & errors. r//Björn L