Re: Classic Traps -- I need your input!

Scott,

My biggest "classic trap" would probably be the tendency to continue to do
things the way they've always been done. This covers a wide range, from a
'rewrite' of an old RPG/400 program which consists simply of replacing every
RPGIII source line with the equivalent RPGIV line (yeah it works, but
really, why bother?) to the tendency to use standard source 'templates' as a
basis for new programs and then never bother to update the templates to take
advantage of newer better techniques. I've seen lots of templates (which I
have nothing against in principle) which use horible old ugly code which
would take an hour or two to update, but it's never done. So instead you get
ugly template source mixed with new fancy source. And it sucks.

Also, how about not using DBGVIEW(*LIST) or DBGVIEW(*ALL) and then realizing
that you accidentally deleted your source...?

Finally, here's my favorite:

Forgetting that after a FOR-loop in RPG, the loop index has been incremented
by 1 more than the upper limit specified in the FOR statement:

for x = 1 to 4;
do stuff
endfor;

X is now 5, *not* 4.

Maybe not a 'classic' trap, though...

Rory