Re: Don't silence fatal errors
| From: | Stanislav Malyshev | Date: | Sun, 10 Feb 2019 01:16:58 +0000 |
| Subject: | Re: Don't silence fatal errors | ||
| References: | 1 2 3 4 5 6 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-104328@lists.php.net to get a copy of this message | ||
Hi!
> My thought that @ mainly relates to another RFC where errors/warning
> are very inconsistently reported or designed (like forcing one to use
> @). 8 would be a good candidate to clean that up, like the TypeError
> RFC.
Cleaning up how PHP does errors would be awesome. After 20+ years of
organic growth without clear standards in this area, we've got a lot of
messy stuff happening there. But I don't think it can solve any
immediate issues - it's not likely that we'll replace every warning in
every extension overnight. It'd be nice if we found some model that
miraculously plugs into existing one and allows to improve things while
keeping everything working. If we get good new APIs - fine, but we'll
need @ to work with old APIs for a while.
--
Stas Malyshev
smalyshev@gmail.com