$include_dir="/home/hyper-archives/boost/include"; include("$include_dir/msg-header.inc") ?>
Subject: Re: [boost] [winapi] Problem with the latest clang on Windows
From: Paul Mensonides (pmenso57_at_[hidden])
Date: 2015-05-31 21:39:45
On 5/31/2015 6:31 PM, Edward Diener wrote:
> On 5/31/2015 8:44 PM, Niall Douglas wrote:
>> On 31 May 2015 at 20:07, Edward Diener wrote:
>> Switching clang into msvc mode makes everything just work.
>
> Clang in MSVC mode means you're dealing with a compiler trying to
> emulate a broken preprocessor. No thanks ! I already had this discussion
> on the clang mailing lists and since they are adamant that they must
> attempt to emulate the VC++ preprocessor bugs in all situations I will
> not use that mode. I suggested to them a system by which they could
> emulate the broken VC++ preprocessor for VC++ headers which need it and
> otherwise support a C++ standard compliant preprocessor everywhere else,
> but they did not want to consider it.
>
> So it doesn't make everything just work. In fact it may break any Boost
> library which uses Boost PP. And that's not a problem which Boost PP is
> going to try to solve.
>
> Boost build also doesn't have built-in support for clang in VC++ mode on
> Windows but works fine with clang in gcc mode on Windows.
Agreed. Clang in MSVC mode is junk.
Regards,
Paul Mensonides