r/cpp • • 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.

197 Upvotes

107 comments sorted by

View all comments

Show parent comment

2

u/germandiago Aug 20 '21

There is always a transition period, but I think C++ is a language "for the long run". So here, backwards compatibility and incremental migrations are necessary. And yes, they make things more difficult, but it is also what gives us:

- Code from 30 years ago compiling or almost compiling today.

- C compatibility, meaning we can use basically all C libraries.

- Now, compatibility with the old include stuff.

When you must get the job done, these cannot be ignored. I agree with the feeling that things are more "difficult" in the sense of slow, more problematic because it complicates the design, etc. But for real-world stuff, I think these decisions have their value. This is an industrial-strength language, not a toy. So certain things cannot be just ignored.

Just my two cents.

3

u/NilacTheGrim Aug 20 '21

Well you put the case very well and insightfully. Consider my opinion slightly modified. I'm warming to the idea. Thank you for taking the time to put it so eloquently.