Un-believable bug

[Holcomb, Katherine A. (kah3f)]

>>(Oh if only fixed format would have been made obsolescent in Fortran
>>90, and removed for Fortran 200x...)
>
>It was certainly obsolescent in Fortran 95.  Removing it is tricky,
>because of Fortran's attitude to dusty decks and the number of them
>still in use.  WG5 would like to do it, but ....

Not compiling dusty-deck code would simply hasten decisions (probably ill
advised in most cases) to convert old code to C++ or such, not to upgrade
to modern Fortran.


>>Multiple statements are apparently not very common. I, for one, have
>>never used them. With a quick grep through the test suite and through
>>roughly 12 million lines of Fortran code from various sources, I
>>couldn't find a single multi-statement line.
>
>There is a good argument for warning about them with -Wextra, because
>they are often confusing and can easily occur by accident (finger
>trouble with ' and ; on UK keyboards, for a start).  What do people
>think?

I use them fairly regularly for short initializations like
a=1.0; b=0.0; c=11.0

Other no-ending-semicolon languages, in particular Python and Swift,
permit multiple-statement lines with semicolon separators, so it seems to
be somewhat standard.

If they were subject to a warning it would definitely need to be one not
turned on by default since it would strike most programmers as peculiar to
warn about a standard language feature.