Regarding compiler extensions

[John4]

Hi,

Probably this question has been answered before, but I just got tired of reading the string "Sorry, no matching items were found for your search. Please try again."

When using the /stand:f95 (or /stand:f03) option, the code lines that are longer than 132 characters generate an error during compilation.Is there any good reason for having considered that particular compiler extension as an error, instead of as a warning. Any other IVF extension generatesjust warnings.

And, is there any way to tell the compiler to ignore some particular warnings during compilation? I ask, because I really don't see the point in the warnings generated by the compiler for every DLLEXPORTed variable it finds.

Thanks in advance for the help.

[Steven_L_Intel1]

When I try it, it shows as an informational, not even a warning level. Are you also setting the /warn:stderror option?

What warnings for DLLEXPORTed variables are you seeing?

There is not currently a way to pick and choose from diagnostics, but this is something we're working on for the future.

[John4]

Yes, by trying an escalated example, I noticed that the 132 characters limit is not the problem... But it is closely related to the problem.

I attachedthe reduced version... The problem seems to be related to the INCLUDEdirective (and I just realized that), but it is solved if the code is restricted to the column limits; for simplicity, I simply put two statements in the same line, but the same error occurs with only one single (and very long) statement.

The funny thing is that I remember to have had the same problemsince the CVF 6.6x (and maybe even with the DVF 5.0x).

The warning for DLLEXPORTed variables occur when you use such variable in another module inside dll.

[Steven_L_Intel1]

Ok, thanks. I see the problem. This is a compiler bug and I'll report it to the developers.

The DLLEXPORT warning is coming from the linker, not the compiler.