Re: [boost] [config] MSVC feature-test macros

Subject: Re: [boost] [config] MSVC feature-test macros
From: Matt Calabrese (rivorus_at_[hidden])
Date: 2018-06-28 18:38:40

On Thu, Jun 28, 2018, 00:56 degski via Boost <boost_at_[hidden]> wrote:

> On 27 June 2018 at 23:21, Stephan T. Lavavej via Boost <
> boost_at_[hidden]> wrote:
>
> > * The macros respect all of our compiler options and library control
> > macros - e.g. if std::byte's definition is suppressed (to avoid conflicts
> > with the Windows SDK), then __cpp_lib_byte reflects that.
> >
>
> I understand this is not really related, but on the issue of macros any
> way. In rpcndr.h there's a macro "#define small char", that is well utterly
> silly to high-jack that word (from the rest of the world), just for the
> sake of defining a longer version of the char type.
>

Yes, especially when it could at least be a typedef. Another one I
encountered a while ago was "hyper" being a #define for a 64-bit int.

>