Re: Line number

On 12/3/2010 9:57 AM, Duane wrote:

This reminds me of an incident a few years ago:

We had a new hire in a 3 person shop. About 2 weeks in she came into my office all bent out of shape, ranting that I had screwed up a program she had been doing maintenance on. I had edited the program to add a small change and saved, which resequenced the line numbers. Well I couldn't do that because now the line numbers didn't match up to the printout she had and she had no idea what lines she changed and the change history (multiple program listings) didn't match up. I pointed her to the date column in the listing and explained it to her and I got to keep my head.

Unfortunately, when you work in a 'mixed shop' - one where some
programmers use SEU and printed listings and others use RDi without them
- those line numbers carry an immense amount of weight. I freely grant
you that in a perfect world those line numbers are of little value in
2010, but we all aren't there quite yet :-)

For the few who must straddle two eras, there is the command line
command: locate sequenceNumber 301 which will find sequence number 3.01

There is also the key binding of locateSequenceLine, which I have set to
c-a-l (ctrl-alt-l)
--buck