qualified name) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit
Has there been any consideration around having MS imply C++11? Given that VC doesn't support modes for standard versions, it wouldn't breaking users expectations as much as requiring that their code is compatible with the most recent version of VC. From: Francois Pichet Sent: 4/19/2012 10:42 PM To: Richard Smith Cc: [email protected]; Nikola Smiljanic Subject: Re: [cfe-commits] Microsoft extension (enum 'enum' used in qualified name) On Thu, Apr 19, 2012 at 5:25 PM, Richard Smith <[email protected]> wrote: > On Thu, Apr 19, 2012 at 2:20 PM, Nikola Smiljanic <[email protected]> > wrote: >> >> On Thu, Apr 19, 2012 at 10:56 PM, Sebastian Redl >> <[email protected]> wrote: >> > The real question is what how much code depends on this. I'm not sure, >> > but I think we generally try not to support every oddity the MS compiler >> > allows, only those that are necessary to parse system headers (including >> > MS-supplied libraries like MFC and ATL) or else are very common. If they >> > just occasionally appear in client code, it would be better to fix that >> > code. >> >> I didn't really think about this :) but you're right, we probably >> don't need this. Francois? > > > Is there a reason that the relevant code can't just be built in C++11 mode > anyway? IIRC Microsoft's compiler doesn't explicitly distinguish between > C++98 and C++11 modes. Agreed, we can already handle such code using -std=c++11. _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits _______________________________________________ cfe-commits mailing list [email protected] http://lists.cs.uiuc.edu/mailman/listinfo/cfe-commits
