Boost logo

Boost :

From: Ruben Perez (rubenperez038_at_[hidden])
Date: 2025-01-13 07:11:37


>
>
>
> In the general case (when a header also defines macros), the public
> header will contain both
>
> import boost.mp11;
>
> and the part that defines the macros, which in Mp11's case is
>
> #include <boost/mp11/version.hpp>
>
> User code wouldn't need to know that in addition to the import,
> it also needs to include a separate macro header.
>

This assumes that macros are "standalone" and don't require including any
stdlib headers. This is the case for mp11/version.hpp and lightweight test,
but is not for Boost.Config or Boost.Charconv headers, for instance. These
may require including <cstddef> or <cstdint> for macros, which need to
happen before any import std. Wouldn't this cause trouble with your scheme?

Thanks,
Rubén.


Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk