Adrian’s Notes

C++ modules and namespaces are said to be orthogonal.

I was very skeptical about the need for internal partitions (a feature provided by C++ modules), but we now found a perfectly valid case for using them in our Windows app (a graphical editor for UML diagrams).

In this blog posting, I would like to analyze a C++ module interface from our UML editor app for Windows.

We’ve now added even more small modules for the Canvas package of our UML editor app for Windows.

We’ve now published a bit more code from our UML Editor Windows app at https://github.com/cadifra/cadifra/tree/2026.7/code.

C++ modules provide a whole new level of information hiding, which is not possible with header files.

There were some discussions about the fact that "module M;" imports the whole interface of M (see “Uneeded Recompilations When Using Partitions”).

As I’ve explained in the posting “Uneeded Recompilations When Using Partitions”, using the syntax "module M;" in implementation files of a module may have the effect of unneded recompilations, if only one external partition of the module is modified.

Our Core module is in code/Core.

The C++ language, as per the current standard, mandates that implementation units of modules implicitly import the interface of the module. // Translation unit #1 export module M; // Translation unit #2 module M; // Translation unit #3 module M; In the…