[cfe-dev] Clang on Windows targeting gcc requirements
popizdeh at gmail.com
Fri Jun 26 04:00:42 PDT 2015
I'm pretty sure they only use EDG for IntelliSense, I'm still seeing code
that compiles fine with VC++ and shows errors from IntelliSense.
Once they decide to get a new frontend I'm sure they'll choose Clang :P
On Fri, Jun 26, 2015 at 8:46 PM, mfaithfull at btopenworld.com <
mfaithfull at btopenworld.com> wrote:
> I looked into this ~18 months ago when I discovered that
> BoostPP disables variadic macros under the VS 2013 preprocessor even though
> compiler v120 officially supports them.
> The combination of having both MSC_VER and __EDG__ defined was not
> correctly handled.
> Given that __EDG__ is an automatic predefine on this compiler I guessed
> Microsoft had switched to EDG. They won't confirm it of course. The closest
> I could get was confirmation from MS that this compiler does have a new
> preprocessor front end and from EDG that they are supplying CPP front ends
> to Microsoft.
> The end result is the same. I'm not sure that the VS CPP is as broken as
> it appears. Other than this bug I've had no trouble with BoostPP under
> MinGW clang or Visual Studio.
> ----- Reply message -----
> From: "Sebastian Redl" <sebastian.redl at getdesigned.at>
> To: <cfe-dev at cs.uiuc.edu>
> Subject: [cfe-dev] Clang on Windows targeting gcc requirements
> Date: Fri, Jun 26, 2015 10:32
> On 26.06.2015 10:40, mfaithfull at btopenworld.com wrote:
> Interesting note on Boost PP. I'm not sure why VC++ is still broken
> given that they have been using EDG front end since 2013?
> AFAIK they're not, only the IntelliSense system is. Where did you hear
> cfe-dev mailing list
> cfe-dev at cs.uiuc.edu
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-dev