Jan Ehrhardt wrote:
Rasmus Lerdorf in php.internals (Tue, 04 Sep 2012 13:15:50 -0700):
>Just call error_reporting() at the beginning of your script.
Which ain't possible in drupal (or hardly). You do not write any code.
You just click together modules, written by others.
Actually Jan - Rasmus is right here - we just have to fix these applications to
bypass problems. It's just a mater of someone who knows how to advancing the
information. But it would be nice if projects like Drupal would indicate what
they plan to do to bring their code in line with PHP's current 'standards'? Or
if not, simply provide the configuration necessary for it to run without
problems on each version of PHP?
I have no problem with it being up to the projects to have to bend to the
changes in PHP, my problem is that some of these bends are not totally thought
out up front and are resulting in a lot of unnecessary work simply to stand
still. generators are a case in point ... why did nobody who understands the
fine detail spot the problem of hidden exceptions? Is it now a done deal that we
have to live with these new ones now, or will an error based provision be made?
It may take some time for me to go through ALL the white screen crashes I've
been creating to cross check their actual cause, but without competent hand
holding correcting mistakes like this, things are going to get missed. That IS
all I have been asking for and the internals list is the only place where these
questions get competent support. Although even here navigating the side issues
can be interesting?
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk
Rainbow Digital Media - http://rainbowdigitalmedia.co.uk
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
