74 …the code looks only slightly different, because one uses an ``import`` declaration rather than a `…
80 …application directly. Preprocessor definitions that precede the import declaration have no impact …
85 … tricks. Moreover, the current preprocessor definitions when an import declaration is encountered …
110 Objective-C Import declaration
112 Objective-C provides syntax for importing a module via an *@import declaration*, which imports the …
118 The ``@import`` declaration above imports the entire contents of the ``std`` module (which would co…
124 …odules at any point within the translation unit, so long as the import declaration is at global sc…
324 …# use.c:4:10: warning: implicit declaration of function 'a' is invalid in C99 [-Wimplicit-function…
477     *module-declaration**
486 Module declaration
488 A module declaration describes a module, including the headers that contribute to that module, its …
492   *module-declaration*:
498 … available when the submodule itself was explicitly named in an import declaration or was re-expor…
523     *requires-declaration*
524     *header-declaration*
525     *umbrella-dir-declaration*
526     *submodule-declaration*
527     *export-declaration*
528     *export-as-declaration*
529     *use-declaration*
530     *link-declaration*
531     *config-macros-declaration*
532     *conflict-declaration*
536 Requires declaration  argument
538 A *requires-declaration* specifies the requirements that an importing translation unit must satisfy…
542   *requires-declaration*:
612 …`std`` module can be extended to also include C++ and C++11 headers using a *requires-declaration*:
630 Header declaration  argument
632 A header declaration specifies that a particular header is associated with the enclosing module.
636   *header-declaration*:
648 A header declaration that does not contain ``exclude`` nor ``textual`` specifies a header that cont…
663 of checking *use-declaration*\s, and must still be a lexically-valid header
677 A given header shall not be referenced by more than one *header-declaration*.
679 Two *header-declaration*\s, or a *header-declaration* and a ``#include``, are
691 Umbrella directory declaration  argument
693 An umbrella directory declaration specifies that all of the headers in the specified directory shou…
697   *umbrella-dir-declaration*:
702 An *umbrella-dir-declaration* shall not refer to the same directory as the location of an umbrella …
709 Submodule declaration  argument
715   *submodule-declaration*:
716     *module-declaration*
717     *inferred-submodule-declaration*
719 A *submodule-declaration* that is a *module-declaration* is a nested module. If the *module-declara…
721 …declaration* that is an *inferred-submodule-declaration* describes a set of submodules that corres…
725   *inferred-submodule-declaration*:
731 …submodule-declaration* shall have either an umbrella header or an umbrella directory. The headers …
733 … is not named by a *header-declaration*, a module declaration is implicitly generated from the *in…
736 * Have the ``explicit`` specifier, if the *inferred-submodule-declaration* has the ``explicit`` spe…
738   *inferred-submodule-declaration* has the ``framework`` specifier
739 * Have the attributes specified by the \ *inferred-submodule-declaration*
740 * Contain a single *header-declaration* naming that header
741 * Contain a single *export-declaration* ``export *``, if the \ *inferred-submodule-declaration* con…
770 Export declaration  argument
772 An *export-declaration* specifies which imported modules will automatically be re-exported as part …
776   *export-declaration*:
784 The *export-declaration* names a module or a set of modules that will be re-exported to any transla…
830 An *export-as-declaration* specifies that the current module will have
835   *export-as-declaration*:
838 The *export-as-declaration* names the module that the current
852 Use declaration  argument
854 A *use-declaration* specifies another module that the current top-level module
860   *use-declaration*:
886 Link declaration  argument
888 A *link-declaration* specifies a library or framework against which a program should be linked if t…
892   *link-declaration*:
897 A *link-declaration* with the ``framework`` specifies that the linker should link against the named…
906 Configuration macros declaration  argument
908 The *config-macros-declaration* specifies the set of configuration macros that have an effect on th…
912   *config-macros-declaration*:
920 A *config-macros-declaration* shall only be present on a top-level module, i.e., a module that is n…
922 The ``exhaustive`` attribute specifies that the list of macros in the *config-macros-declaration* i…
954 A *conflict-declaration* describes a case where the presence of two different modules in the same t…
958   *conflict-declaration*:
961 The *module-id* of the *conflict-declaration* specifies the module with which the enclosing module …
998 Any *identifier* can be used as an attribute, and each declaration specifies what attributes can be…
1135 …slation unit are ignored. See the section on the `Configuration macros declaration`_ for more info…