Bug #16

Fixing a TRAP in DevAnalyzer when reusing FOR-loop variables

Added by J. Templ about 5 years ago. Updated about 5 years ago.

Status:ClosedStart date:09/29/2014
Priority:NormalDue date:
Assignee:I. Denisov% Done:


Target version:1.7
Forum topic:


When reusing a FOR-loop variable in a nested FOR-loop, DevAnalyzer
generates a TRAP due to an invalid CASE label instead of
reporting error 910 (for loop variable set).
The invalid CASE label results from adding the constant 'noChange' (=16)
to the loop variable's 'num' field for every nesting level.

Reported by Ivan Denisov on 2013-09-02.
Open Point 41 in BB 1.6 release.
CPC 1.7 change list item 44.

Associated revisions

Revision 4465d3f5
Added by J. Templ about 5 years ago

Bug fix as suggested by Ivan Denisov and CPC 1.7 change list. Refs: #16.
Simplification in UseObj and generalization to arbitrary nesting levels in SetObj by Josef Templ.

Revision cb7d892a
Added by J. Templ about 5 years ago

Merge pull request #5 from BlackBoxCenter/issue-#16

Refs: #16.


#1 Updated by J. Templ about 5 years ago

  • Status changed from New to Closed

Also available in: Atom PDF