From 11e94aa1106b7ff16844023ef4a58b4ac4cf5459 Mon Sep 17 00:00:00 2001 From: Peter Klausler <35819229+klausler@users.noreply.github.com> Date: Tue, 19 Mar 2019 10:14:23 -0700 Subject: [PATCH] [flang] Update FortranForCProgrammers.md Original-commit: flang-compiler/f18@39d81438442cc1185409240842084338c2c5d276 Reviewed-on: https://github.com/flang-compiler/f18/pull/341 --- flang/documentation/FortranForCProgrammers.md | 9 +++++++-- 1 file changed, 7 insertions(+), 2 deletions(-) diff --git a/flang/documentation/FortranForCProgrammers.md b/flang/documentation/FortranForCProgrammers.md index ffc2882..7ac119c 100644 --- a/flang/documentation/FortranForCProgrammers.md +++ b/flang/documentation/FortranForCProgrammers.md @@ -1,5 +1,5 @@ Fortran For C Programmers @@ -278,10 +278,15 @@ Preprocessing There is no standard preprocessing feature, but every real Fortran implementation has some support for passing Fortran source code through a variant of the standard C source preprocessor. -Behavior varies across implementations and one should not depend on +Since Fortran is very different from C at the lexical level (e.g., line +continuations, Hollerith literals, no reserved words, fixed form), using +a stock modern C preprocessor on Fortran source can be difficult. +Preprocessing behavior varies across implementations and one should not depend on much portability. Preprocessing is typically requested by the use of a capitalized filename suffix (e.g., "foo.F90") or a compiler command line option. +(Since the F18 compiler always runs its built-in preprocessing stage, +no special option or filename suffix is required.) "Object Oriented" Programming ----------------------------- -- 2.7.4