in reply to
Re: When should you not use strict and warnings?
in thread When should you not use strict and warnings?
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
