L
Laura Stern
Guest
Re "there is no way to trap the error message of a STOP condition ... then that's the first thing that can be fixed" The rationale behind changing existing STOP conditions to ERROR is two-fold. One is that we then do not have to invent a new mechanism to trap STOP error messages. We already have 2 mechanisms, NO-ERROR and CATCH. We don't need yet another one. Secondly, most conditions that raise STOP are not really different from any other error condition. "File not found" is a good example. Historically (wayyy back) this was deemed to be more serious than other errors since it implied that there was something seriously wrong with the app installation. Thus the STOP condition. But with the advent of tooling and frameworks, etc. the distinction is now just a meaningless historical artifact. Even if we do this, there will probably still be STOP conditions - e.g., from STOP AFTER and from CTRL-C. But neither of these has an error message associated with it.
Continue reading...
Continue reading...