mirror of
https://github.com/intel/llvm.git
synced 2026-01-21 04:14:03 +08:00
[flang][NFC] Document semantics of an ambiguous/non-portable use case
We intentionally process NAMELIST groups in a scope after having resolved all of the names in that scope. This means that a name whose first appearance in a scope is in the NAMELIST group resolves to a local object, if any, rather than to any host associated object. The standard is unclear on this point, and there is no clear precedent in other compilers. This patch doesn't implement this choice -- that was done long ago -- but just documents the behavior in Extensions.md. Differential Revision: https://reviews.llvm.org/D154375
This commit is contained in:
@@ -581,6 +581,13 @@ end module
|
||||
* F18 allows `OPTIONAL` dummy arguments to interoperable procedures
|
||||
unless they are `VALUE` (C865).
|
||||
|
||||
* F18 processes the `NAMELIST` group declarations in a scope after it
|
||||
has resolved all of the names in that scope. This means that names
|
||||
that appear before their local declarations do not resolve to host
|
||||
associated objects and do not elicit errors about improper redeclarations
|
||||
of implicitly typed entities.
|
||||
|
||||
|
||||
## De Facto Standard Features
|
||||
|
||||
* `EXTENDS_TYPE_OF()` returns `.TRUE.` if both of its arguments have the
|
||||
|
||||
Reference in New Issue
Block a user