in reply to Warnings and Strict in Production/Performance
I would guess that use warnings; has some performance cost, if for no other reason than checking for cases like "Use of uninitialized value in print at..." costs something.
On the other hand, having a program terminating silently is a bad thing: how will anybody know whether it died, let alone how? Sometimes performance is given excess value. After all, nobody should care how rapidly they're given the answer "4" to the question "what is the sine of 4500 radians?" Similarly, the program should do a bit more than silently vanish away when a question like "what is the sin-1(1.5)?" is asked.
emc
At that time [1909] the chief engineer was almost always the chief test pilot as well. That had the fortunate result of eliminating poor engineering early in aviation.
—Igor Sikorsky, reported in AOPA Pilot magazine February 2003.
|
|---|