Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:105460
MIME-Version: 1.0
References: <5c633ed8.1c69fb81.143ab.ad85@mx.google.com> <CAEQoxLLncOfiSvB23=yTOF8D5D0Ba=YC96eqP0XWJXAz5xw6Yg@mail.gmail.com>
 <CAG9XoMT1WFLKMjC1o6mPkvv4zPu1D+6NpgP9VYx4ppYocjRmjw@mail.gmail.com>
 <CAEQoxLL8a6DhyDmEdBbNUfGCqy04UeLAK6HQO=zYrVbGG2w40w@mail.gmail.com>
 <CAG9XoMQkZYP9wNNu0tQYTcuWJPx=4u7NfSdPCQDjo7O3o02OxA@mail.gmail.com>
 <6a97cecf-7a5d-6476-7773-fdd41aa45646@gmx.de> <CAG9XoMStfqmDqjQ7SMSZXEbvXvSAh_YwstjF67+nSumCh_5s4A@mail.gmail.com>
 <CAEQoxLLxB715OSUkM8OYs+3z9E8kLe45zrEh5sT7gx00r1waZA@mail.gmail.com>
In-Reply-To: <CAEQoxLLxB715OSUkM8OYs+3z9E8kLe45zrEh5sT7gx00r1waZA@mail.gmail.com>
Date: Fri, 26 Apr 2019 15:10:13 +0200
Message-ID: <CAG9XoMSWub7GhmMhiwmhdXN7v+nubzkmtyJm7r8Gq3FzVDr4rA@mail.gmail.com>
To: Vladyslav Startsev <vladyslavstartsev@gmail.com>
Cc: "Christoph M. Becker" <cmbecker69@gmx.de>, "Legale.legale" <legale.legale@gmail.com>, 
	Ben Ramsey <ben@benramsey.com>, PHP Internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000076422605876ea8fb"
Subject: Re: [PHP-DEV] Make bcmath functions more strict
From: benjamin.morel@gmail.com (Benjamin Morel)

--00000000000076422605876ea8fb
Content-Type: text/plain; charset="UTF-8"

> Yes, PHP 8 for BCs and PHP 7.4 for warnings that's what I was trying to
said

FWIW, I don't think anyone will complain about adding a warning to
something that's obviously a bug when it fails.
I'd say go ahead a write an RFC. If you want to have more chances for it to
pass though, I would not change the semantics of the current conversions
from string to decimal (what's considered a valid decimal number and what's
not). I would just propose to add a warning when an argument is converted
to zero because it is *currently* considered malformed.

- Ben

--00000000000076422605876ea8fb--