Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fix several bugs in array type handling in dotnet module
Several bugs were present in the parsing and generation of a string to represent an array type, notably when the "lo_bound" value is set. - The "read_blob_signed" was buggy for values outside the [-2**6, 2**6-1], the sign edition did not use the right bitmask, and the type used was unsigned. - The display when lo_bound != 0 was buggy: - size=5, lobound=0 => should be `5`, this was ok - size=5, lobound=1 => should be `1...5`, this was buggy and displayed `1...6`. The "range format" is inclusive. - 0 should still be displayed if size is 0. Only when size is unset should it be left out. So an array declared as `[5,0,3]` should be displayed the same way, and not as `[5,,3]`.
- Loading branch information