------- Comment #5 from burnus at gcc dot gnu dot org 2010-08-17 07:54 ------- (In reply to comment #4) > There was some history regarding legacy codes as the reason why this does not > error out. ie looping back and trying again was a feature. I think I may put > this behind -std=legacy. It does seem odd the way we are doing this now.
Can you give an example how to use this? For "?", "=", and "=?" this does not seem to be needed as one does not return to the program. And while I see a reason for staying in the dialog when an error occurs (i.e. to enter a correct namelist), immediately returning to the program without setting iostat/=0 or jumping to the err= label seems odd to me. -- I tried hard but I still fail to come up with any usage scenario where it makes sense. Unless we find a (even remotely) useful usage scenario, I would not even enable it with -std=legacy. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=45108
