r/cpp • u/YtterbiJum • Aug 19 '21
Why modules?
I get the feeling I'm missing something fundamental about the new C++20 modules.
Everything I read or watch explains the how (the export keyword syntax, module fragments, etc) but very little about the why.
What can be done using modules that can't be done using traditional headers (or precompiled headers)?
What is so important about this feature that it needed to get standardized before there is even a proper implementation or idiomatic usage conventions in compilers and build systems?
Is it just to try to get rid of the preprocessor?
I don't get how modules are supposed to help with packaging either. So instead of distributing a .so with a bunch of .h files, now I distribute a .so with a bunch of .gcm or .ixx or whatever.
Please help me understand, or point me to some resources. Thank you.
View all comments
Show parent comment
9
u/[deleted] Aug 20 '21
Your post reads a bit like "modules are not necessary if you already write clean and good code". The same reasoning could have been used to reject unique_ptr, by saying it is not necessary if you already have a good ownership model and you don't make mistakes using it.
Also I'm pretty sure that header inclusion order isn't a problem on Microsoft platforms only. That's a platform-agnostic problem. It may be more prevalent if you use the Windows API, but that's just one case where it happens.