Now let's talk about what to do when your program is having trouble.
A program can go wrong in any number of ways. Maybe it won't run at all. A look at the error messages, especially the first line or two of the error messages, usually leads you to the problem, which will be somewhere in the syntax, and its solution, which will be to use the correct syntax (e.g., matching braces or ending each statement with a semicolon).
Your program may run but not behave as you planned. Then you have some problem
with the logic of the program. Perhaps at some point, you've zigged when you should
have zagged, like adding instead of subtracting or using the assignment operator
= when you meant to test for equality
between two numbers with
==. Or, the problem
could be that you just have a poor design to accomplish your task, and it's only
when you actually try it out that the flaw becomes evident.
However, sometimes the problem is not obvious, and you have to resort to the heavy artillery.
Fortunately, Perl has several ways to help you find and fix bugs in your programs.
The use of the statements
use warnings; should become a
habit, as you can catch many errors with them. The Perl debugger gives you complete
freedom to examine a program in detail as it runs.
In general, it's not too hard to tell when the syntax of a program is wrong because the Perl interpreter will produce error messages that usually lead you right to the problem. ...