Bug #78143 [Opn->Nab]: SoapClient::__construct with no arguments cannot be caught

Edit report at https://bugs.php.net/bug.php?id=78143&edit=1 ID: 78143 Updated by: cmb@php.net Reported by: gadelat at gmail dot com Summary: SoapClient::__construct with no arguments cannot be caught -Status: Open +Status: Not a bug Type: Bug Package: SOAP related Operating System: linux PHP Version: 7.3.6 -Assigned To: +Assigned To: cmb Block user comment: N Private report: N New Comment: Well, the first parameter to SoapClient::__construct() is supposed to be mandatory, this is not even a change that should be documented, but rather the mentioned bug fix established the proper behavior. Previous Comments: ------------------------------------------------------------------------ [2019-06-11 14:15:22] cmb@php.net This behavioral change has been introduced by fixing bug #77088. ------------------------------------------------------------------------ [2019-06-11 12:47:42] gadelat at gmail dot com Description: ------------ So this is PHP 7.3 BC break and I can't find it in https://www.php.net/manual/en/migration73.incompatible.php Constructing SoapClient with no arguments can no longer be caught. It's very likely other classes are affected as well. Where can I read about this BC break? PS: Sorry for not selecting soap package when creating issue, but I don't see it anywhere in a list Test script: --------------- try { new SoapClient(); } catch (Throwable $e) {} // PHP 7.2 no output, PHP 7.3 result: Warning: SoapClient::SoapClient() expects at least 1 parameter, 0 given in php shell code on line 1 ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=78143&edit=1