Warnings question

[nvaneck]

Is there a way to turn off the standards warningfor lines > 132 and for invalid charqter in name, e.g. the $ sign when standard checking?

I like to use lines that fit my screen for claritybut manyexceed 132 characters. Also, when using quickwin there are a lot of names in the include files that contain $. This generates a lot of useless warnings on a large project and makes it hard to see the real stuff.

The help files refer to an option to exclude certain messages by message number but these don't have any.

Thanks!

[Steven_L_Intel1]

I see numbers.

E:Projects>ifort /c /nologo /stand t.f90
t.f90(1): warning #5142: Invalid use of $ character in identifier
integer foo$bar
---------------^
t.f90(2): warning #5268: Extension to standard: The text exceeds right hand column allowed on the line.
print *, '1234567890123456789012345678901234567890123456789012345678901234567890
123456789012345678901234567890123456789012345678901234567890'
--------------------------------------------------------------------------------
----------------------------------------------------^

E:Projects>ifort /c /nologo /stand /Qdiag-disable:5142,5268 t.f90

E:Projects>

[nvaneck]

Quoting - Steve Lionel (Intel)

I see numbers.

E:Projects>ifort /c /nologo /stand t.f90
t.f90(1): warning #5142: Invalid use of $ character in identifier
integer foo$bar
---------------^
t.f90(2): warning #5268: Extension to standard: The text exceeds right hand column allowed on the line.
print *, '1234567890123456789012345678901234567890123456789012345678901234567890
123456789012345678901234567890123456789012345678901234567890'
--------------------------------------------------------------------------------
----------------------------------------------------^

E:Projects>ifort /c /nologo /stand /Qdiag-disable:5142,5268 t.f90

E:Projects>

Intersting; I don't...

includeRESOURCE.FD(132) : Warning: Invalid use of $ character in identifier
D:ProjectsMicrOsirisSUBSDIALCOM.F90(14) : Warning: Extension to standard: The text exceeds right hand column allowed on the line.

Did this change after 10.1?

[Steven_L_Intel1]

Oh, you're using 10.1. Yes, it did. The use of error numbers by the language-part of the compiler was new for 11.0.

[nvaneck]

Quoting - Steve Lionel (Intel)

Oh, you're using 10.1. Yes, it did. The use of error numbers by the language-part of the compiler was new for 11.0.

Thanks, Steve.

Further exploration after your previous reply finds that it works for static verification, but you must run the whole solution, and you get many more undesired messages and still get the normal diagnostics/warnings...

Is a release 12 coming soon?

Regards, Neal

[Steven_L_Intel1]

In version 10.1, the Static Verifier (now called Source Checker) messages did use numbers, as did some optimizer messages, but not those from the Fortran "front end". Yes, Static Verifier is likely to give you a lot of messages.

No, I would not say a release 12 is soon. 11.1 will be with us for quite a while.