Toby Ewing wrote:
But for when I don't ;-), and in lieu of a complete range checking implementation, would it be easier to write a stand-alone program parser that would examine a program for potential range-checking errors?
Unless someone has a brilliant idea to do with very easily, I don't think it would be easier. In some cases it's even impossible (when the bounds depend on variables' values, the "parser" would have to simulate the program's behaviour which can only be done for specific cases, cf. halting problem).
Frank