Re: [boost] So.... what are we going to do about modules?

...

Neil Douglas wrote: It's clever enough to interpret an include as an import. So no need.

I know this is the case with clang, but what about gcc and msvc?

...

Peter Dimov wrote: My ambitions are modest. All I want is to be able to do this: #if BOOST_MODULES_SUPPORTED

import <cstddef>; import ; import <exception>; import ; import <utility>; import <functional>; // std::hash import <cstdint>; import <iosfwd>;

#else

#include <cstddef> #include #include <exception> #include #include <utility> #include <functional> // std::hash #include <cstdint> #include <iosfwd>

#endif

You may also want to declare the above as a module itself so you can import it elsewhere :)

...

John Maddock wrote:

...

Is there any existing best practice we should follow yet?

Unfortunately, not yet. And I’m not sure that there will be — at least not until some package management support makes its way into the standard. WL

On Apr 5, 2022, at 2:31 PM, Peter Dimov via Boost wrote:

Daniela Engert wrote:

...

Right, but this part of the standard is optional. MSVC has it but not the others, right?

I can find /translateInclude in the documentation but according to the description it doesn't automatically translate stdlib includes.

_______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost