Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59002
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain thelounge.net designates 91.118.73.15 as permitted sender)
Message-ID: <4F65C87A.70703@thelounge.net>
Date: Sun, 18 Mar 2012 12:35:22 +0100
Organization: the lounge interactive design
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:11.0) Gecko/20120316 Thunderbird/11.0
MIME-Version: 1.0
To: internals@lists.php.net
References: <4F65A77F.3010001@lsces.co.uk>
In-Reply-To: <4F65A77F.3010001@lsces.co.uk>
OpenPGP: id=7F780279;
	url=http://arrakis.thelounge.net/gpg/h.reindl_thelounge.net.pub.txt
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature";
 boundary="------------enigF951B918E037CDC69D964A17"
Subject: Re: [PHP-DEV] PHP5.4 'nannying'
From: h.reindl@thelounge.net (Reindl Harald)

--------------enigF951B918E037CDC69D964A17
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable



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

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


--------------enigF951B918E037CDC69D964A17
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk9lyHoACgkQhmBjz394AnlYeQCfd2u6fcjrcZhb1U2u7Fj85klz
WgIAoJv5YMzrtJkziWAsflBdCFB8+CLA
=jhvI
-----END PGP SIGNATURE-----

--------------enigF951B918E037CDC69D964A17--