Re: Documenting code changes

This sounds like a RPG only solution. And it uses what used to be
reserved for card sequences when you used to type out RPG on 80 or 96
column cards. Nowadays I hate anything in my sequence numbers and I
immediately blank that out. Also, in RDi I tell it not to show that area.
It is just clutter. I can see how some people might think that an entry
here would really stick out (if they had blanked out all ancient sequence
numbers first).
I'll leave that up to personal preference and not dogma.
Here's the deal, why have a different shop standard depending on which
language you are using? Why not use the same, adapting only to
specifications imposed by the language? For example, the difference
between a comment in cl and the // comment in rpg-free.

Maybe this isn't a good example but hopefully it get's my point across.
123456789012345
MOD01 x=x*1.05;

let's say MOD01 was to change the percent from 4 to 5 percent.
MOD02 was 6, MOD03 was 7, MOD04 was 5.25 and so on.
How would your source now look?

Please, no comments from the peanut gallery on why the percent shouldn't
be hardcoded. I am just using an example.

Rob Berendt