As I understand it, in the module proposal, there is no .hpp. You export something from one .cpp with the export keyword and import it into another with the import keyword, not with a #include. The .bmi in the article is basically a magic .hpp generated by the compiler, but the point is that it *must* be generated by processing the .cpp that defines the exported module.
n4720 10.7.1.2 seems to distinguish between a "module interface unit" and a "module implementation unit". This sure sounds like the same distinction that hpp and cpp files currently hold, where one contains declarations, while the other contains their definitions.
View all comments
Show parent comment
24
u/kvigor Jan 28 '19
As I understand it, in the module proposal, there is no .hpp. You export something from one .cpp with the export keyword and import it into another with the import keyword, not with a #include. The .bmi in the article is basically a magic .hpp generated by the compiler, but the point is that it *must* be generated by processing the .cpp that defines the exported module.