Ticket #1654 (closed bug: invalid)

Opened 5 years ago

Last modified 4 years ago

ops2c should complain about ops numbering in ranges

Reported by: plobsing Owned by:
Priority: normal Milestone:
Component: build Version: 2.4.0
Severity: low Keywords:
Cc: Language:
Patch status: Platform:

Description

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.

Change History

Changed 4 years ago by jkeenan

  • component changed from none to build

Would it be possible to write a test which illustrates the problematic case?

Thank you very much.

kid51

Changed 4 years ago by plobsing

  • status changed from new to closed
  • resolution set to invalid

ops.num is no more. with that, this ticket becomes meaningless.

Note: See TracTickets for help on using tickets.