Re: When should you not use strict and warnings?

Replies are listed 'Best First'.
Re^2: When should you not use strict and warnings? by CountZero (Bishop) on Dec 27, 2012 at 15:55 UTC
Clearly an instance of killing the messenger that brings bad news. CountZero A program should be light and agile, its subroutines connected like a string of pearls. The spirit and intent of the program should be retained throughout. There should be neither too little or too much, neither needless loops nor useless variables, neither lack of structure nor overwhelming rigidity." - The Tao of Programming, 4.1 - Geoffrey James My blog: Imperial Deltronics	[reply]
Re^2: When should you not use strict and warnings? by MidLifeXis (Monsignor) on Dec 27, 2012 at 14:13 UTC
Without testing? In production? Ewwww. Or was it due to the number of 'bugs that now need to be fixed'? --MidLifeXis	[reply]
Re^2: When should you not use strict and warnings? by Anonymous Monk on Dec 27, 2012 at 19:27 UTC
I hope he's glad he got the hell out of thatplace before a production failure that they never even cared to look-for was blamed on him. I've certainly seen good people get canned for that ... and they dusted the soles of their shoes as they departed.	[reply]