Poor project settings in RFortran

*** What steps will reproduce the problem?

1. Compile/build RFortran (any configuration)

*** What is the expected output?

Compiled/built library where:

1) The compiler carries out the maximum number of checks of the code (for
subroutine interfaces being correct, that all vars are initialized, etc)

2) compile/build warnings relate solely to extensions genuinely needed for
the required functionality.

*** What do you see instead?

1) Current project settings disable most if not all compile-time checks

2) Enabling these checks leads to lots of warnings relating to
non-necessary extensions such as "Extension to standard: The text exceeds
right hand column allowed on the line", "Tab formatting", etc....

*** Please provide any additional information below.

1) Disabling compile-time checks is not a very good idea. Needless to say
this just allows bugs to slip and stay in the code (cf "uninitialized FLAG"
in issue 40).

2) While seemingly just esthetic, reducing the number of warnings to the
bare minimum is very helpful for the code development.

Having 1000's of unnecesary warnings clutters the build log and simply
results in important warnings (such as un-initialized variables, etc) being
overlooked. In turn this hides bugs and delays development.

Of course warnings related to truly needed features are also useful by
indicating in what aspects is the code non-conformant.

Original issue reported on code.google.com by dmitri.k...@gmail.com on 6 Aug 2009 at 6:29

hodgesse1 / rfortran

Poor project settings in RFortran #41