Whereas a typo in a variable name can introduce subtle and difficult to find bugs, a typo in a subroutine name ALWAYS blows up in a spectacular way as soon as you try to access the non-existing subroutine.
And yes, it will only happen at run-time, but if you are in the habit of deploying your scripts into production without any tests or even a few private runs on your dev-box, then you probably deserve the lesson your irate user will bring to you.
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
In reply to Re: Detecting undefined subroutines at compile time
by CountZero
in thread Detecting undefined subroutines at compile time
by bdenckla
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |