Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59003
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain managedit.ie designates 209.85.210.170 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <4F65A77F.3010001@lsces.co.uk>
References: <4F65A77F.3010001@lsces.co.uk>
Date: Sun, 18 Mar 2012 12:53:10 +0000
Message-ID: <CAGSj+QutjeiHms5PckAQ6O8tk4Wn9k629yWqxzXn+3TTJu6WAA@mail.gmail.com>
To: Lester Caine <lester@lsces.co.uk>
Cc: PHP Internals List <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=14dae93404bf89eb2c04bb83ecd3
Subject: Re: [PHP-DEV] PHP5.4 'nannying'
From: kiall@managedit.ie (Kiall Mac Innes)

--14dae93404bf89eb2c04bb83ecd3
Content-Type: text/plain; charset=ISO-8859-1

May I suggest changing the error reporting value, that way we can stop
hearing about your damn code ;)

Seriously though, I doubt anyone has a guide like that.

I know I've always had E_STRICT enabled and honestly don't have the
slightest clue how to trigger a strict warning. When you develop with it
on.. you just don't make those mistakes and identify new issues as they
happen. Not 10 years of mistakes and depreciations at once.

Your best bet is to disable strict warnings in production, and chip away at
them as they show up on your development server.

Thanks,
Kiall

Sent from my phone.
On Mar 18, 2012 9:15 a.m., "Lester Caine" <lester@lsces.co.uk> wrote:

> OK having jumped through several hoops trying to get a stable installation
> of Apache2.4.1 with PHP5.4 and Firebird 2.5.1 I now have a machine running
> and while I've not been able to do a speed comparison as yet performance
> does seem to be improved on what a simple comparison of machine speed
> improvement would suggest.
>
> Being a 6 core processor, on does wonder if better threaded performance of
> PHP with Apache would be an advantage? But the main problem now is handling
> an array of 'nanny' messages telling me that the code is badly written.
> Since the code base has been developed form an environment where it was
> still PHP4 compatible, many of the 'incremental improvements' of PHP5.2 and
> PHP5.3 have yet to be addressed, so I suspect that while the code runs
> clean with 'display_errors' ON in 5.3.10 I suspect every one of several
> hundred files now needs to be modified to include things like
> 'private/protected/static' correctly in every base and descendent class? Of
> cause things are not helped when PEAR packages add their own array of
> warnings, but the main problem is where the heck to start on this.
>
> 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 ...
>
> --
> Lester Caine - G8HFL
> -----------------------------
> Contact - http://lsces.co.uk/wiki/?page=**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<http://www.firebirdsql.org/index.php>
>
> --
> PHP Internals - PHP Runtime Development Mailing List
> To unsubscribe, visit: http://www.php.net/unsub.php
>
>

--14dae93404bf89eb2c04bb83ecd3--