|
293 | 293 | it's an error only if the resolution is ambiguous.
|
294 | 294 | * An entity may appear in a `DATA` statement before its explicit
|
295 | 295 | type declaration under `IMPLICIT NONE(TYPE)`.
|
296 |
| -* INCLUDE lines can start in any column, can be preceded in |
| 296 | +* `INCLUDE` lines can start in any column, can be preceded in |
297 | 297 | fixed form source by a '0' in column 6, can contain spaces
|
298 | 298 | between the letters of the word INCLUDE, and can have a
|
299 | 299 | numeric character literal kind prefix on the file name.
|
|
312 | 312 | a portability warning.
|
313 | 313 | The Fortran standard doesn't allow `SIZE=` with formatted input
|
314 | 314 | modes that might require look-ahead, perhaps to ease implementations.
|
| 315 | +* When a file included via an `INCLUDE` line or `#include` directive |
| 316 | + has a continuation marker at the end of its last line in free form, |
| 317 | + Fortran line continuation works. |
315 | 318 |
|
316 | 319 | ### Extensions supported when enabled by options
|
317 | 320 |
|
|
439 | 442 | This is especially desirable when two generics of the same
|
440 | 443 | name are combined due to USE association and the mixture may
|
441 | 444 | be inadvertent.
|
442 |
| -* Since Fortran 90, INCLUDE lines have been allowed to have |
| 445 | +* Since Fortran 90, `INCLUDE` lines have been allowed to have |
443 | 446 | a numeric kind parameter prefix on the file name. No other
|
444 | 447 | Fortran compiler supports them that I can find.
|
445 | 448 | * A `SEQUENCE` derived type is required (F'2023 C745) to have
|
|
0 commit comments