Dear all,

Dear all,

in this message (Wed, 03/23/2011 - 07:08):

Quote:

Steve Lionel (Intel) wrote:

I admit that it is a bit confusing that we have collected various categories of compile-time diagnostics under -warn, but not all of these are strictly warnings. For example, "-warn declarations" is the equivalent of IMPLICIT NONE and will give you errors (not warnings) for undeclared variables.

[...]

I think this is not true. I am looking for a way to stop compilation when a variable is not declared, and none of the options "-warn declarations" and "-implicitnone" make ifort stop and return a non-zero error status (and therefore stops the makefile).

This is something that I really miss about ifort. I understand that some warnings can be safely ignored and fixed when one has time (I have many of these so I can't use -warn errors), but this one means that ifort has automatically chosen a type and kind that is very likely not to be the correct one (we could make some statistics on how often a programmer intended to use a REAL*4 variable starting with a "A" letter). In other words, except when porting old code to new code, it is not safe to continue when this warning is raised.