C++ Logo


Advanced search

Terminology for tooling (Was: P2581R0: Specifying the Interoperability of Binary Module Interface Files)

From: Daniel Ruoso <daniel_at_[hidden]>
Date: Thu, 5 May 2022 10:57:42 -0400
Em qui., 5 de mai. de 2022 às 03:47, Daniela Engert via SG15
<sg15_at_[hidden]> escreveu:
> I'm not too happy with overloading the term 'visible' yet
> another time beyond what the standard is already ascribing
> to it. Your description above is what the standard is telling us
> in [module.reach] paragraphs 1 and 2.

Yes. I agree. So here it is revised once again:

1. "Importable Module Units": Any translation unit that needs to be
reachable (presumably through binary module interface files) for the
parsing of a different translation unit.

   1.1. "Primary Module Interface Unit": The translation unit with
"export module foo;".

   1.2. "Module Interface Partition Units": The translation units with
"export module foo:baz"

   1.3. "Module Implementation Partition Units": The translation units
with "module foo:bar"

 2. "Non-importable Units": Translation units that do not influence
the parsing of other translation units.

    2.1. Module implementation units: Translation units with "module foo;"

    2.1. Non-modular translation units: Everything else

Received on 2022-05-05 14:57:55