search for: vcblog

As of Visual Studio 2015, natvis files can be included as part of individual projects <http://blogs.msdn.com/b/vcblog/archive/2015/09/28/debug-visualizers-in-visual-c-2015.aspx>, a much better method than manually copying the file to an specific directory in %USERPROFILE%. I think it should be included in one of the CMakeLists.txt files, does anybody know how I can add it? Sincerely, Alexander Riccio -- &quot...

MSVC survives because there's no effective competition- it's like communications providers in the United States or political parties in China. The alternatives like GCC have no decent development environments for them, and Clang has the bonus of not being mature w.r.t. things like Standard libraries. The reality is, there's nowhere to go *but* MSVC. This stuff is the major reason why

...smooth because of GCC / libstdc++ issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. > Just my 2c. > > [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ <https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/> > On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com <mailto:echristo at gmail.com>> wrote: > Once ag...

...in any time soon, and from what I gather, nobody has any more reservations about moving to C++17 than they do about moving to C++14. They only have reservations about moving to anything at all. So if we're gonna move, we should go all the way. Just my 2c. [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> wrote: > Once again, I'm totally down for this and think we should do it. I worry > about windows, but ... > > Zach: How's windows c++14 suppo...

...indows and ARM and x86 for Windows Phone. * Write a wrapper to integrate codec into Windows Media Platform * Create NuGet package or Extension SDK and publish it (the simplest part :)) Also offloading some parts of the computation to the GPU with C++ AMP <http://blogs.msdn.com/b/vcblog/archive/2011/06/15/introducing-amp.aspx> would be useful Andrii. -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/opus/attachments/20140610/69ff3b31/attachment-0001.htm

...#39;s slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. >>>> >>>> >>>> >>>>> Just my 2c. >>>>> >>>>> [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ <https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/> >>>>> >>>>> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com <mailto:echristo at...

...sted in collecting representative IR from frontends other than Clang. There is also some discussion about these results [on the mailing list](http://article.gmane.org/gmane.comp.compilers.llvm.devel/88588). Microsoft have [open sourced their GDB/LLDB 'debug engine'](http://blogs.msdn.com/b/vcblog/archive/2015/07/20/source-now-available-for-gdb-lldb-debug-engine.aspx). ## On the mailing lists * Piotr Padlewski has [shared a plan to improve Clang's devirtualization](http://article.gmane.org/gmane.comp.compilers.clang.devel/44022) which he will be working on with Richard Smith at Google...

...++ > issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow > move out of C++11 I’d rather get C++14 now rather than a painful transition > to C++17 that drags on as we discover issues. > > > > Just my 2c. > > [1] > https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ > > On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> > wrote: > > Once again, I'm totally down for this and think we should do it. I worry > about windows, but ... > > Zach: How's w...

.../ libstdc++ issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. > > >> Just my 2c. >> >> [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ <https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/> >> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com <mailto:echristo at gmail.com>> wrote: >>...

...xable, but given LLVM's slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. >>> >>> >>> >>>> Just my 2c. >>>> >>>> [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ <https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/> >>>> >>>> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com <mailto:echristo at gmail....

...bstdc++ > issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow > move out of C++11 I’d rather get C++14 now rather than a painful transition > to C++17 that drags on as we discover issues. > > > Just my 2c. > > [1] > https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ > > On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> > wrote: > >> Once again, I'm totally down for this and think we should do it. I worry >> about windows, but ... >> >> Z...

...n’t been super smooth because of GCC / libstdc++ issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. Just my 2c. [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com<mailto:echristo at gmail.com>> wrote: Once again, I'm totally down for this and think we should do it. I worry about windows, but ... Zach: How's win...

...9;s slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. >>>> >>>> >>>> >>>>> Just my 2c. >>>>> >>>>> [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ <https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/> >>>>> >>>>> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com <mailto:echristo a...

...6 and GCC 7. It’s all fixable, but given >> LLVM's slow move out of C++11 I’d rather get C++14 now rather than a >> painful transition to C++17 that drags on as we discover issues. >> >> >> Just my 2c. >> >> [1] >> https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ >> >> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> >> wrote: >> >>> Once again, I'm totally down for this and think we should do it. I worry >>> about windows, but...

...n’t been super smooth because of GCC / libstdc++ issues in both GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow move out of C++11 I’d rather get C++14 now rather than a painful transition to C++17 that drags on as we discover issues. Just my 2c. [1] https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com<mailto:echristo at gmail.com>> wrote: Once again, I'm totally down for this and think we should do it. I worry about windows, but ... Zach: How's win...

...6 and GCC 7. It’s all fixable, but given >> LLVM's slow move out of C++11 I’d rather get C++14 now rather than a >> painful transition to C++17 that drags on as we discover issues. >> >> >> Just my 2c. >> >> [1] >> https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ >> >> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> >> wrote: >> >>> Once again, I'm totally down for this and think we should do it. I worry >>> about windows, but...

On Sun, Jan 13, 2013 at 7:39 PM, David Blaikie <dblaikie at gmail.com> wrote: > On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> > wrote: > >> Good points David, I don't feel qualified to evaluate the differences > >> between those versions though... Perhaps Richard or Doug could comment > here? > > > > Unless

On Sun, Jan 13, 2013 at 10:26 AM, Tim Northover <t.p.northover at gmail.com> wrote: >> Good points David, I don't feel qualified to evaluate the differences >> between those versions though... Perhaps Richard or Doug could comment here? > > Unless I'm misreading the buildbots, we don't actually have anything > trying to build with MSVC. Have we considered how

...th GCC 6 and GCC 7. It’s all fixable, but given LLVM's slow move > out of C++11 I’d rather get C++14 now rather than a painful transition to > C++17 that drags on as we discover issues. > > > > > > Just my 2c. > > > > [1] > https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ > > > > On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> > wrote: > > Once again, I'm totally down for this and think we should do it. I worry > about windows, but ... > > > &g...

...7. It’s all fixable, but given >> LLVM's slow move out of C++11 I’d rather get C++14 now rather than a >> painful transition to C++17 that drags on as we discover issues. >> >> >> >> Just my 2c. >> >> [1] >> https://blogs.msdn.microsoft.com/vcblog/2018/05/07/announcing-msvc-conforms-to-the-c-standard/ >> >> On Thu, May 10, 2018 at 11:18 AM Eric Christopher <echristo at gmail.com> >> wrote: >> >> Once again, I'm totally down for this and think we should do it. I worry >> about windows, but ... &gt...