2017-11-29 0:03 GMT+01:00 Nikita Popov <nikita....@gmail.com>: > In summary, the first two commits combined were not a BC break -- they only > removed a warning and made an error message nicer. After the third commit > we now *do* have a BC break, because what was previously a SodiumException > is now an E_ERROR. > > I hope we can restore some sanity to this world by reverting that revert...
All in all, E_ERROR should *never* be used by an extension, we should revert back to using an Exception and re-tag the 7.2.0 release asap -- regards, Kalle Sommer Nielsen ka...@php.net -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
