On Wed, 30 Mar 2022 at 16:26, Seymour J Metz <[email protected]> wrote: > Yes, range checking carries a performance penalty, and there have been > arguments in the past about performance versus safety. I'm in the camp that > believes that they should be enabled in any program where incorrect output > would cause a problem or where there are security issues.
While working at a client in the late 1990'ies development compiles used all checking prefixes, production compiles used SUBSCRIPTRANGE, and that was occasionally triggered in CICS, users always manage to outsmart the most fool-proof code. Of course in PL/I you should never ever used hardcoded array bounds in DO-loops, but rather the "LBOUND()", "HBOUND()" and "DIM()" builtins! Robert -- Robert AH Prins robert(a)prino(d)org The hitchhiking grandfather <https://prino.neocities.org/index.html> Some REXX code for use on z/OS <https://prino.neocities.org/zOS/zOS-Tools.html> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
