On 05 февр. 2014 г., at 13:43, Lester Caine <[email protected]> wrote:
> Ferenc Kovacs wrote:
>> For general purpose applications (like drupal/wordpress/etc.) it wouldn't
>> be useful either, because they want nice and descriptive error screens
>> instead of php fatal errors which would most of the time just result in a
>> blank screen and some lines in the error log.
>
> This is perhaps one of the areas that would benefit from some improvement in a PHP6 roadmap. It
> IS all too easy to get a blank screen already without adding more? Invariably when an ISP upgrades
> their PHP service a number of their client sites simply give a white screen, and in many cases the
> users have no idea where to go next? More verbose responses actually on screen would be a little
> more constructive. Performance improvements are all very well, and do have a place, but a white
> screen is no use at all? Certainly it's a not uncommon result these days when upgrading PHP
> versions ...
well, idea is that production web-sites should never report details of their inner workings
(including errors) on screen.
error-report is in the error-log.
but nice useful errors are a benefit of their own, so I hope that PHP6 will have
https://wiki.php.net/rfc/engine_exceptions
--
Alexey Zakhlestin
CTO at Grids.by/you
https://github.com/indeyets
PGP key: http://indeyets.ru/alexey.zakhlestin.pgp.asc
Attachment: [application/pgp-signature] Message signed with OpenPGP using GPGMail signature.asc