BlackBox Framework Center

A poll is now open to use the solution suggested by Josef to flag modification of an index variable.
The discussion of that issue is here

In order to cast an informed vote I would like to see a precise definition of the bug - just a single code example that fails does not adequately document the nature of the problem. As a minimum, something on the lines of (assuming my understanding is correct):

DevAnalyzer in Blackbox 1.6 Final identifies when an index variable is modified within a FOR loop.

However in a very specific rare case it results in a trap:

1. There is a nested FOR loop

AND

2. The same index variable is used for each FOR loop

AND

3. The index variable is assigned to another variable within the FOR loop

If the fix solves other instance of traps then they should also be clearly identified. I would also like to see some evidence that regression testing has been done using other relevant code samples to ensure that the fix does not have any unwelcome side effects.

This voting is also finished.

The fix covers only cases that failed before because there were INVALID,
i.e missing, labels in some CASE statements.
For anything else there is exactly the same behavior as before.
I have done some testing and I have not observed anything unexpected.

Of course, it would be nice to have an automated test suite that performs this
kind of regression testing. Unfortunately we don't have it now and it is not on the horizon.

For test cases see http://forum.blackboxframework.org/view ... f=40&t=101.

- Josef