Isize values are provided to qsv in an ini file that is supplied at runtime.
At present, if invalid (lower bound is greater than upper bound) values are supplied, the application will keep on going, with unknown consequences.
The aims of this PR are to examine the isize values provided and throw an exception as early as possible should invalid values be present.
Fixes #142
Type of change
Please delete options that are not relevant.
[X] Bug fix (non-breaking change which fixes an issue)
How Has This Been Tested?
Code has been tested against an ini file with invalid/valid isize values and fails/proceeds accordingly.
Existing unit tests pass
Checklist:
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have made corresponding changes to the documentation
[X] My changes generate no new warnings
[X] New and existing unit tests pass locally with my changes
Description
Isize values are provided to qsv in an ini file that is supplied at runtime. At present, if invalid (lower bound is greater than upper bound) values are supplied, the application will keep on going, with unknown consequences.
The aims of this PR are to examine the isize values provided and throw an exception as early as possible should invalid values be present.
Fixes #142
Type of change
Please delete options that are not relevant.
How Has This Been Tested?
Code has been tested against an ini file with invalid/valid isize values and fails/proceeds accordingly. Existing unit tests pass
Checklist: