Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-19 Thread Richard Lynch
On Sun, March 18, 2012 6:35 am, 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 >>

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Lester Caine
Forgot the pigging reply all :( Nikita Popov wrote: On Sun, Mar 18, 2012 at 6:53 PM, Lester Caine wrote: > [...] SO my original question still applies, but for different > reasons ... is there a crib sheet to help eliminate strict code errors in > legacy code bases? Uhm, I'm not sure wheth

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Reindl Harald
Am 18.03.2012 18:53, schrieb Lester Caine: > Ferenc Kovacs wrote: >> * *|E_ALL|* now includes *|E_STRICT|* level errors in the error_reporting >> >> >> configuration >> directive. >> >> I would guess your

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Nikita Popov
On Sun, Mar 18, 2012 at 6:53 PM, Lester Caine wrote: > [...] SO my original question still applies, but for different > reasons ... is there a crib sheet to help eliminate strict code errors in > legacy code bases? Uhm, I'm not sure whether I am completely stupid and miss something obvious: But wh

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Lester Caine
Johannes Schlüter wrote: This list is not for user support. This list is for future development. Please help all here to keep it productive. Thanks. And hopefully to educate developers to understand some of the problems that they are creating by their actions? -- Lester Caine - G8HFL -

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Lester Caine
Ferenc Kovacs wrote: * *|E_ALL|* now includes *|E_STRICT|* level errors in the error_reporting configuration directive. I would guess your code was running clean, because you didn't have E_STRICT in your

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Johannes Schlüter
On Sun, 2012-03-18 at 15:53 +, Lester Caine wrote: > 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 ... See http://php.net/migrati

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Ferenc Kovacs
On Sun, Mar 18, 2012 at 4:53 PM, Lester Caine wrote: > 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 cer

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread 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 ... usuall

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Pierre Joye
hi Lester, Discussing periodically about the introduction of new notices or warnings in releases is not very fun and interesting. Good habits and related topics can be discussed on the php general mailing list or any other support channels. Thanks for your understanding, On Sun, Mar 18, 2012 at

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Kiall Mac Innes
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

Re: [PHP-DEV] PHP5.4 'nannying'

2012-03-18 Thread Reindl Harald
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