| April 2006 |
|---|
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| |
|
|
|
|
|
1 |
| 2 |
3 |
4 |
5 |
6 |
7 |
8 |
| 9 |
10 |
11 |
12 |
13 |
14 |
15 |
| 16 |
17 |
18 |
19 |
20 |
21 |
22 |
| 23 |
24 |
25 |
26 |
27 |
28 |
29 |
| 30 |
|
|
|
|
|
|
|
|
Unraveling Code with the Debugger
 Reading other people's code can be difficult, especially if you have no idea what happens when and where. Understanding code flow is vital to maintenance and bug fixes, but littering code with print and debugging statements is tedious and prone to error. There's another way: use the debugger! Daniel Allen demonstrates how to pinpoint a problem with Perl's debugger.
Read the entire article here
posted at: 1:04am on 10-Apr-2006
path: /Programming/Perl | permalink | edit (requires password)
| April 2006 |
|---|
| Sun |
Mon |
Tue |
Wed |
Thu |
Fri |
Sat |
| |
|
|
|
|
|
1 |
| 2 |
3 |
4 |
5 |
6 |
7 |
8 |
| 9 |
10 |
11 |
12 |
13 |
14 |
15 |
| 16 |
17 |
18 |
19 |
20 |
21 |
22 |
| 23 |
24 |
25 |
26 |
27 |
28 |
29 |
| 30 |
|
|
|
|
|
|
|
|