Re: how to get CVF not to compile when more than 132 characters on a line?




"dpb" <none@xxxxxxx> wrote in message news:fqjq7b$tei$1@xxxxxxxxxxx
louisrom1@xxxxxxxxx wrote:
I use .f90 files and I cannot change the extension
is there a way to limit to 132 characters?

Set Standard-checking to F95 and "Warn on source truncation"

In the IDE these are in Compilation Diagnostics under Project Settings...

For some reason the "Standard warning as error" didn't trigger a fatal
error, but did the warning on a test program. It appears exceeding the
132 column Standard line length didn't make the list of Standard
violations, but is checked against the line truncation.

So, didn't _stop_ compilation outright, but does provide a warning.
Halfway good enough? :)

--

The "Standard warning as error" does not seems to give any warning but
"Fortran Standard Checking" set to "Fortran 90" or Fortran 95" gives
an "Info" notation, at least with CVF 6.6.C which I think was the last
version before Intel took over.

The standard has since 66 mostly talked about requirements on the program,
not on the compilers. Thus compilers silent has truncated lines on most
platforms I have used, only shouted if the statement in some ways became
errornous when truncatred.

Kurt


.



Relevant Pages

  • Re: Inconsistent Program Results
    ... including one of them might trivially slow down compilation, ... I wrote the above (starting with "The standard headers"). ... return void, but there's no advantage in using that. ... You're cheating yourself by ignoring warning messages. ...
    (comp.lang.c)
  • Re: Trigraphs forever
    ... since a "diagnostic" only needs to be a warning. ... What the standard doesn't have is requirements that compilation shall ... fail at certain times. ...
    (comp.std.c)
  • Re: how to get CVF not to compile when more than 132 characters on a line?
    ... Set Standard-checking to F95 and "Warn on source truncation" ... For some reason the "Standard warning as error" didn't trigger a fatal ... So, didn't _stop_ compilation outright, but does provide a warning. ...
    (comp.lang.fortran)
  • IA64 (2.6.3 - 2004-02-20.17.30) - 309 New warnings (gcc 3.3.1)
    ... make: warning: Clock skew detected. ... :10306: Warning: This is the location of the conflicting usage ... {standard input}:10315: Warning: Only the first path encountering the conflict is reported ...
    (Linux-Kernel)
  • 2.6.22-rc3-mm1: IA64 make allnoconfig broken
    ... {standard input}:12494: Warning: Only the first path encountering the conflict is reported ... :12493: Warning: This is the location of the conflicting usage ...
    (Linux-Kernel)