Re: errors after upgrade vom 5.2.10 to 5.3.0 howto solve or hide?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 16 February 2011 14:34, Daniel P. Brown <daniel.brown@xxxxxxxxxxxx> wrote:
> On Wed, Feb 16, 2011 at 07:15, Richard Quadling <rquadling@xxxxxxxxx> wrote:
>> On 16 February 2011 11:25, Andre Polykanine <andre@xxxxxxxx> wrote:
>>> Hello Fotoo,
>>>
>>> Â Â Â Â Â <?
>>> error_reporting(0);
>>
>> Really?
>>
>> You consider shoving your head in the sand a REALISTIC option?
>
> Â ÂWell, at the least, it would shut the errors up in the meantime,
> pending an actual resolution. ÂHowever, the use of short_open_tags may
> completely defeat the intended purpose.
>
> --
> </Daniel P. Brown>
> Dedicated Servers, Cloud and Cloud Hybrid Solutions, VPS, Hosting
> (866-) 725-4321
> http://www.parasane.net/
>

Because some of the code has been edited, it is now broken. Hiding the
errors at that stage is really driving with your eyes closed.

If the changes are reverted, so that ereg is still used rather than
preg, and the deprecation notices suppressed, then that maybe the best
place to be for the short term.


-- 
Richard Quadling
Twitter : EE : Zend
@RQuadling : e-e.com/M_248814.html : bit.ly/9O8vFY

-- 
PHP General Mailing List (http://www.php.net/)
To unsubscribe, visit: http://www.php.net/unsub.php




[Index of Archives]     [PHP Home]     [Apache Users]     [PHP on Windows]     [Kernel Newbies]     [PHP Install]     [PHP Classes]     [Pear]     [Postgresql]     [Postgresql PHP]     [PHP on Windows]     [PHP Database Programming]     [PHP SOAP]

  Powered by Linux