Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59005
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain lsces.co.uk from 213.123.26.186 cause and error)
Message-ID: <4F6604DC.4040308@lsces.co.uk>
Date: Sun, 18 Mar 2012 15:53:00 +0000
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.2) Gecko/20120215 Firefox/10.0.2 SeaMonkey/2.7.2
MIME-Version: 1.0
To: PHP internals <internals@lists.php.net>
References: <4F65A77F.3010001@lsces.co.uk> <4F65C87A.70703@thelounge.net>
In-Reply-To: <4F65C87A.70703@thelounge.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] PHP5.4 'nannying'
From: lester@lsces.co.uk (Lester Caine)

Reindl Harald wrote:
>
> Am 18.03.2012 10:14, schrieb Lester Caine:
>> >  I think what I am probably looking for is a clean guide as to how code SHOULD be written nowadays in order to avoid
>> >  the nanny messages since it's certainly not my normal practice after 10 years of coding in PHP5 ...
> usually it would have been enough if you had used full error-reporting
> from very first start and fixed deprecated warnings long ago
The code IS running clean in PHP5.3 and we had this same discussion back when 
all the deprecated warnings came in ... it took some months to get to a point 
where the error log was clean again ...

> this way i am maintaining a CMS with around 250000 LOC since 2003
> and did every major PHP-upgrade wgere it is used and distributed on
> some hundret domains without any problem
>
> any code which does not run with E_STRICT is not allowed to
> run on our sevrvers and so the are no compromises needed
> yes, so easy is life if someone decides not support any crap
Ditto ... which is why the reams of new messages are what is somewhat confusing. 
The code runs fine and switching off the warnings prevents the logs growing at a 
rapid rate,
I'm happy to run with display_errors = on because if an error does crop up we 
prefer to know about it fast.

So I need to work out why with PHP5.4 we have such an overload of warning 
messages ... so I CAN fix them ... which is why I'm asking here for advise on 
migration information to a clean code base in PHP5.4 ...

-- 
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//
Firebird - http://www.firebirdsql.org/index.php