Jeff Karr wrote:
> With COBOL/370, the compiler option SSRANGE can
> force an abnormal end to processing at the point
> the program tries to exceed the range of
> the table. The failure message displays the line
> number and the name of the table with the problem.
> With this option turned off (NOSSRANGE),
> processing continues but you risk storage overlay
> problems and failures even in other programs depending
> on how wild the subscript value is.
I worked with I*M mainframe COBOL compilers where table misalignment
caused memory corruption, with-out any compile or run-time warnings or
errors.
For TC, I think the best approach would be a compile time traps for
literals indexes which are out of range, and a run-time option
(htrtconf) to deal with identifier indexes which are out of range.
I will try to add these features before the next TC release.
|
