http://gcc.gnu.org/bugzilla/show_bug.cgi?id=53077
Bug #: 53077
Summary: suggestion to add the .f extension to the list of file
extensions that trigger enabling of the preprocessor
Classification: Unclassified
Product: gcc
Version: 4.8.0
Status: UNCONFIRMED
Severity: enhancement
Priority: P3
Component: fortran
AssignedTo: unassig...@gcc.gnu.org
ReportedBy: sla...@staszic.waw.pl
Hello,
$ cat test.f
#define print(x) print*, x
program test
print('aqq')
end
$ gfortran -ffree-form test.f
Warning: test.f:1: Illegal preprocessor directive
test.f:3.8:
print('aqq')
1
Error: Missing leading left parenthesis in format string at (1)
$ mv test.f test.F
$ gfortran-mp-4.6 -ffree-form test.F && echo OK
OK
This behavior is consistent with the docs but it's quite misleading, especially
as the warning message might be understood as if there was something wrong
within the macro definition, and not with the fact that the macro is there at
all.
Why not turning on the preprocessor with .f extensions as well?
(currently only the .F extension turns it on by default)
HTH,
Sylwester
