Date: Wed, 20 Apr 2022 15:06:04 -0400
On Wed, Apr 20, 2022, 14:59 Tom Honermann <tom_at_[hidden]> wrote:
> I'm having a hard time with the notion that the answer to "How do I
> build C++ Hello World using a modularized standard library?" would be
> "First, choose and install a build system that works with your compiler".
...
> Some things we really need to keep at least as simple as they are today
> and introducing a build system requirement doesn't do that.
I don't think that expectation is realistic. C++ Modules are
semantically several orders of magnitude more complex than what we had
with the preprocessor.
We went from "it's fine if you just concatenate all files together and
compile to an executable" to "the module parsing context is
independent from the translation unit that consumes it".
And this is a *really good thing*. We'll finally be able to ship
reusable code that is not going to be subject to the random variations
generated by the preprocessor on the caller side.
daniel
> I'm having a hard time with the notion that the answer to "How do I
> build C++ Hello World using a modularized standard library?" would be
> "First, choose and install a build system that works with your compiler".
...
> Some things we really need to keep at least as simple as they are today
> and introducing a build system requirement doesn't do that.
I don't think that expectation is realistic. C++ Modules are
semantically several orders of magnitude more complex than what we had
with the preprocessor.
We went from "it's fine if you just concatenate all files together and
compile to an executable" to "the module parsing context is
independent from the translation unit that consumes it".
And this is a *really good thing*. We'll finally be able to ship
reusable code that is not going to be subject to the random variations
generated by the preprocessor on the caller side.
daniel
Received on 2022-04-20 19:06:16