Ticket #1654 (closed bug: invalid)
ops2c should complain about ops numbering in ranges
|Reported by:||plobsing||Owned by:|
ops2c complains about every op that has inconsistent numbering (between what it calculates and ops.num). If an early op (eg: band) gets added or removed, all subsequent ops get shifted by a constant amount, making one problem output 1100 lines of error (or warning) message.
It would be nice if ops2c output inconsistent ops numbering in ranges of constant offset, which would make one change correspond to one line of diagnostic.