OK - I've got PHP5.3.0-dev up at the moment in order to test the Firebird
stuff, so display_errors is on. I need it on anyway while testing code.
The 'problem' I am having is that of cause none of the other PHP stuff I'm
using is currently not compatible with PHP5.3 so generates a lot of deprecated
warnings in particular.
Current one is phpDocumentor which uses is_a() extensively, and has a function
to replicate it for backwards compatibility.
Short of switching display_errors on and off all the time, how do other people
handle this irritation? I could repair phpDocumentor in this case and ignore
BC as I will not be running THAT on older version of PHP, and since a run is
taking 30 minutes it would be interesting to see if there is any improvement
to time.
.... bit the bullet - my copy of phpDocumentor has no is_a() in it ....
--
Lester Caine - G8HFL
-----------------------------
Contact - http://lsces.co.uk/lsces/wiki/?page=contact
L.S.Caine Electronic Services - http://lsces.co.uk
EnquirySolve - http://enquirysolve.com/
Model Engineers Digital Workshop - http://medw.co.uk//
Firebird - http://www.firebirdsql.org/index.php
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
