Re: IF NOT %FOUND

On Tue, Nov 12, 2019 at 5:13 PM Craig Richards <craig@xxxxxxxxxxxxxxxx> wrote:

And if some maintenance programmer drops a READ into the loop?

It would only be a problem if he dropped his READ in between the last two
lines, in between the READE and the ENDDO.

They could drop in a read statement followed by ITER.

Then my version would work correctly and yours wouldn't.
That would be ironic - the very thing you put in to defend
against potential mistakes, caused an issue, where otherwise the code would
have been ok

I'm not 100% sure what you're envisioning, but if "not working
correctly" entails something very obvious (preferably a compile-time
error, but failing that, a run-time error, and failing that, hopefully
some kind of really, really blatant and easily visible wrong
calculations) then there's an argument to be made that it's a good
thing.

Obviously, there is no way to defend against everything. Sometimes,
making it harder to be *subtly* wrong is a win. (I mean that in
general. Whether your example is an illustration of this, I am not
sure, since I didn't fully follow it.)

John Y.