I read this and I think "shell script". Do you have a set of tools you use when youre programming? For example, the above procedure could easily be accomplished by something like this:
(forgive the shellness of the example, and I havent tested it either) -- but this would ensure that you have a working copy saved, that it is good, and you can continue to develop on the new copy. If you train yourself to pause every 12 lines, or (where i usually break) every new sub, you could save yourself a lot of time. I have a lot of scripts like this, I'm curious if you use anything like that.#!/usr/local/bin/bash [ perl -c "$1" ] && cp "$1" "`echo $1| sed 's:.pl::g'`.bak.pl" && vim "$1"
And yeah, you did recently post something on debugging, and I remember upvoting it. After looking in the Secret Search I see:
I'm sure i'm missing stuff.
brother dep.
--
Laziness, Impatience, Hubris, and Generosity.
In reply to Re: Re: Are debugging skills atrophying?
by deprecated
in thread Are debugging skills atrophying?
by dws
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |