Missing Compile Warning (I think)

[jackosullivan]

Does IVF no longer catch the use of a variable before it is defined?

If I recall correctly, when using CVF6.6 in MS Developers Studio and IVF 8+ in MSVS.NET2003, I could force warnings to be treated as errors, and the compilerwouldkeep me from trying to use a variable before I defined it. Even though this did not work well with variables in COMMON, this was a marvelous way to catch misspellings.

Now, with 9.1.3663.2003 in MSVS.NET 2003 SP1, I've been a several-day victim of its missing at least one such screw-up that was not associated with a COMMON.

Is this option no longer available? Or have I missed one of the better-hidden options in the Project Properties?

Or is it perhaps fixed in IVF10?

Thanks and God bless!

Jack

[Steven_L_Intel1]

In Intel Fortran, uninitialized variable checking is done at run-time and not compile time. It is an optional setting in Visual Studio under "Run-Time". The class of things it will pick up is different from CVF due to different compiler technologies being used.

[Steven_L_Intel1]

However, you should also try the new Static Verifier option in 10.0 - it will catch a lot of things CVF did and more.

[jackosullivan]

Thanks, Steve, for the speedy and as usual right-to-the-point answer(s).

Looks like you just tipped me over the edge into the IVF10 bin ... despite it being mid-project.

Thanks again and God bless!

jack