Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:107933 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 968 invoked from network); 20 Dec 2019 02:33:29 -0000 Received: from unknown (HELO php-smtp3.php.net) (208.43.231.12) by pb1.pair.com with SMTP; 20 Dec 2019 02:33:29 -0000 Received: from php-smtp3.php.net (localhost [127.0.0.1]) by php-smtp3.php.net (Postfix) with ESMTP id B02042C05C4 for ; Thu, 19 Dec 2019 16:34:01 -0800 (PST) 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.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS3215 2.6.0.0/16 X-Spam-Virus: No Received: from mail-vs1-xe36.google.com (mail-vs1-xe36.google.com [IPv6:2607:f8b0:4864:20::e36]) (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 ; Thu, 19 Dec 2019 16:34:01 -0800 (PST) Received: by mail-vs1-xe36.google.com with SMTP id b4so4524054vsa.12 for ; Thu, 19 Dec 2019 16:34:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wKao7Qt7zN/YhuroMqQESrq4/ZmxymkQY9uwaN5a9Gc=; b=jqrnRusJXUpyGFXLCN1ylhsW9RPqjCIfE4jz9yEN3LIVTi2Xhupsx94J6ztrynGd76 Ad1KN8mGKz8ubWG3oSRenV918fhOFow006OWVV5p20vNc9nJ7Q6MJg1X5QWcUhF5hoXw zChxlWql9AYGKnSg21oGkx4n8DQ9XnVlgNQjSNn9mmDU4iEzPqFryXlNgpNlTyucEFjJ r9mcw2DU9auE4dYfk+YNPhweITPNG50RXPgBVBHdwD29Iu67v1FdBkTQufDK62IKZC6a 61ibovlqnoqc7JGCZJ71nBSNjqSUdGYK0cml8QYGYtpUSJWLaULPSsimbMEXoro2pvv+ KIIQ== 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=wKao7Qt7zN/YhuroMqQESrq4/ZmxymkQY9uwaN5a9Gc=; b=jHv2A657aNlvnLIKIXF3BTfLnx3tjvsUGQObX5+VdheR2SLC5TKCfAvm0wZZODwwoG 4LuilpP3pZ5npMGO1MrljxfA+tnvYWXfhArH5em/cy2MMAUkV2T/EB1RoX0C25lQrmc0 kHb8jfdXDG2XeWafRWWY+Rrut4QDwn2IqlgUm8TIPZB7WZ1hwXDnuslRXHy3ifwHxsy3 c9b7bbUijf4qT28fZRZg2c6sRIuUMDnfLxdgh/5W0DrMl5outJulpai1eqrEWOKJeQyq 8lxbNtZKcZbVHfWzvH3I2lT6Wu9rgx3hIl877sxFR8IIstJO487vudPZI64+emI5FQLD 3EYA== X-Gm-Message-State: APjAAAV43qzbSWkHFA1HPr7Xv1dJ47//0iS28ZiLhIrDzNR6huJAqQLk JJ5Tgk19B5whynsatJAAA3aR5OWRTK2j8hC+xNA= X-Google-Smtp-Source: APXvYqxM5wkJK9jH2elk/yPrHjk4WZ8L743NzKSKWVJHKHuz6U8ikr6sbITxMC6AH/13+VURvFRNkF164sQqtSQbNno= X-Received: by 2002:a05:6102:3034:: with SMTP id v20mr7157772vsa.28.1576802040759; Thu, 19 Dec 2019 16:34:00 -0800 (PST) MIME-Version: 1.0 References: <49beea16-31ab-d7f9-54e6-8d46a5331f3d@gmail.com> In-Reply-To: <49beea16-31ab-d7f9-54e6-8d46a5331f3d@gmail.com> Date: Fri, 20 Dec 2019 01:33:49 +0100 Message-ID: To: Rowan Tommins Cc: PHP Internals Content-Type: multipart/alternative; boundary="000000000000854855059a17d5a6" X-Envelope-From: Subject: Re: [PHP-DEV] Changelog / upgrading notes for promoted warnings From: george.banyard@gmail.com ("G. P. B.") --000000000000854855059a17d5a6 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, 19 Dec 2019, 21:17 Rowan Tommins, wrote: > Hi all, > > Earlier, I was writing an application-specific wrapper around the > password_hash function, and was surprised that it could return false, > rather than throwing an error. > > I then found this commit to master making it throw errors for PHP 8.0: > https://github.com/php/php-src/commit/37c11714 > > That's great! But ... it is a breaking change, and I can't see any note > in UPGRADING. Is there a running list of the Warnings that have been > promoted to Errors anywhere, and if not, should we create one before we > forget? > > Regards, > > -- > Rowan Tommins (n=C3=A9 Collins) > [IMSoP] > As there are a lot more of these promotion, from what I recall, is that a general upgrading note will be added. As the promotions cover case which are clear programming/logic errors and thus shouldn't arise in production code. An example of a promotion is an invalid flag value (e.g. a mode with fopen which does not exist) or out of bound values (usually integer value which need to be greater than zero). Moreover, I'm not sure it's helpful to have a massive list of functions where some warnings have been promoted and others not. But this is only my opinion. Best regards George P. Banyard > --000000000000854855059a17d5a6--