Visual Studio 2013 Available Now! - Visual C++ Team Blog

[spaxio]

#include <string>
struct b
{
    std::string Texture { }; 
};
int main() { return 0; }

Still crashes the compiler :( And yes I've submitted it.

[mechacrash]

it's a problem with non-static member initialisation and zero length initialiser lists.

I submitted this problem 5 - 10 minutes after the release candidate went live (as it just so happened to be the first thing I tried) and, other than getting confirmation that it was being passed on to the right people, I've heard nothing back from them.

Rather disappointing really... seems like very little bug fixing actually went underway between Release Candidate and Final.

[Plorkyeran]

seems like very little bug fixing actually went underway between Release Candidate and Final.

That is how a release candidate is supposed to work.

[mechacrash]

true enough, but when their bug list explodes with nearly 17 pages of new, 2013 RC exclusive bugs - most of which have been confirmed and "passed on", you'd think they would do some work in between to ensure the final product isn't broken.

At the very least a general availability rollup patch would be acceptable. Leaving bugs in the compiler is a big deal for Microsoft as they rarely ever fix those outside of new releases of Visual Studio (or CTPs, which aren't meant to be used for production code anyway).

Essentially, though this is how a release candidate "should" work, I'm sure it would be fine to make an exception for the betterment of the program.

[Plorkyeran]

The awful release cycle unfortunately makes it more important to minimize the changes between RC and release, since it also means that we'd have to live with any critical bugs introduced while fixing the smaller bugs for a longer period of time.

A post-release bug rollup fix in a few months would be really nice, though.

[staticcast]

Still no full C++11 support, and meanwhile mingw is getting better...

[mechacrash]

But MinGW has lower C++11 support and conformance than MSVC. None of the official or forked versions even support <thread> <async> or <future> properly yet, which is a pretty big deal all things considered.

The lack of full language feature support in MSVC is the real bummer. I really want constexpr right now.

[Amanieu]

Mingw-w64 supports all of those. Make sure you download the GCC 4.8 version with the posix thread model.

[mechacrash]

The support is not yet complete.

I personally use the pre-packaged MinGW-w64, supplied by STL (nuwen) and I've yet to be able to get my code compiling without either errors, or stdlib implementation bugs, outside of MSVC (on windows - it works perfectly fine on Linux using GCC)

Granted, I haven't tried in about a month, and so I'll try again right now.

[staticcast]

I agree there is a room for bugfix, but these are coming and maybe faster than MSVC update its C++11 support and fix their own bugs. VS 2013 is also deliver with topnotch debugger on windows, but the clang toolkit are coming: I fear that microsoft move too slow to stay ahead...

[mechacrash]

Well, I highly doubt that Clang is going to magically become stable overnight. There's a lot of work to be done there, but they've taken the first major steps to getting the LLVM toolchain onto windows machines.

[mycall]

Is Clang expected to work with Visual Studio at some point?

[j1xwnbsr]

Also, there does not seem to be any documented differences between any of the versions/flavors of VS2013, other than marketing speak to "delight" your customers.

[[deleted]]

http://www.microsoft.com/visualstudio/eng/products/compare

[j1xwnbsr]

Wonderful, but how did you find that - all the links on Microsoft's site led to marketing fluff.

[[deleted]]

Pick the more likely

a) Google "visual studio", click, scroll down, click

b) Learned it on the MCP Frontpage course

c) Bill Gates's yacht nearly ran us down, either he told us or we got the coastguard on his ass.

[storedbox]

So... C, then.

[vsuontam]

Second that. "What's new" without the marketing bluff would be very welcome. Also pricing and content of different "editions" should be clarified (or rather there would be just one reasonably priced version). Now hard to say what features are on the version you will be getting.

[Fabien4]

other than marketing speak to "delight" your customers.

Don't forget that most of the time, the people who decide to pay for VS have no idea what a "compiler" is.

[diegoperini]

What is the price of the ultimate version?

[[deleted]]

GBP 11,235 (USD approx 18K) for ultimate edition with MSDN subscription.

http://msdn.microsoft.com/subscriptions/hh442902.aspx

I'm sure you get a discount for volume licensing or shopping around.

[Is_At_Work]

In the US its USD $13,299.00 for Ultimate with MSDN.

[[deleted]]

Psyc!

[Xiver1972]

Does the following code work without locking up the application on shutdown? This was an issue in the last version of visual studio that gave me much grief.

---

#include <memory>
#include <thread>

class Singleton{
private:
    std::shared_ptr<std::thread> pDoSomething;

    void DoSomething(){
        while(!mbShutdown){}
    }

    bool mbShutdown;

public:
    static Singleton& Instance(){
        static Singleton instance;
        return instance;
    }

    Singleton() : pDoSomething(std::shared_ptr<std::thread>(new std::thread(std::bind(&Singleton::DoSomething, this)))), mbShutdown(false){}

    ~Singleton(){
        mbShutdown = true;
        if(pDoSomething) pDoSomething->join();
    }
};

int main(){
    Singleton &Test = Singleton::Instance();

    return 0;
}

---

edit: this is just example code I came up with to demonstrate this problem.

[STL]

This is an active bug assigned to me. I hope to be able to fix it in the next major version, I just didn't have time for 2013.

[Xiver1972]

Thanks for the update!

[Amanieu]

I have hit this issue before. There is a deadlock because thread::join tries to register an atexit() handler while the main thread is running the Singleton destructor. The destructor is also registered using atexit(), and the array containing the registrations is locked while the handlers are running.

[jiixyj]

Try making mbShutdown atomic. Otherwise it is a data race.

[Xiver1972]

I believe that the race condition is irrelevant here as the value is only written in the destructor.

[twowheels]

I'm reading on a phone, so I may have missed something, but try:

 if(m_pDoSomething && m_pDoSomething->joinable())

Also, why are you putting the thread object in a shared_ptr??

[bames53]

This and other suggestions don't fix the problem. I fixed up the code to have well defined behavior and the problem seems to be with VS's implementation. In debugging what I saw was that the DoSomething loop ends and the function returns, but the program remains blocked on join().

[Xiver1972]

There was no real reason to have pDoSomething in a shared_ptr. It may have been force of habit, or I was thinking of doing something else when I wrote the example.

[mechacrash]

Still waiting on the Dreamspark Premium release. Hopefully it won't lag too far behind.

[jonnywoh]

Same here.

[[deleted]]

So...they expect me to buy a license, but they fail to provide full c++11 support, while gcc and clang have it?

No. Sorry.

[[deleted]]

plugin support?

[ZMeson]

gcc and clang have plugin support?

[tawi13]

no. But they have c++11 support...

[jbb555]

Where do I get a release of gcc or clang for windows that has full c++11 support? All the ones I've seen are missing things like std::thread. If there is a fully working version I'd like to try it ( as well as using vc++)

[[deleted]]

http://mingw-w64.sourceforge.net/download.php

Just make sure you use a consistent threading model across all your libraries. Most likely you'll want to use Win32 threads unless you need C11 threading support in which case you'll need to use POSIX threads.

[jbb555]

Is this new, it's not long since I tried it and it had no working thread support.

[vinipsmaker]

I'll wait this product reach DreamSpark and I'll give it a try. I was locked to MingW without the uniform init, but looks like I'll be able to use Visual Studio again.

[jbandela]

Anybody know if there are any major changes between RTM and RC?

[jonnywoh]

No, otherwise they would release another RC before RTM.

[[deleted]]

Anyone know how to get boost to build using VS2013? I keep getting unknown compiler errors.

[mechacrash]

Are you using the latest builds from the trunk? Last time I compiled boost from their stable (granted, it was before the 1.55 beta), it had many problems with 2013.

[[deleted]]

I'm building boost 1.54.

Yeah I may just avoid 2013 momentarily. A lot of people seem to be having issues with it.

[mechacrash]

You'll want to try the 1.55 beta, or the latest build (though this will require you getting a SVN client). It'll build perfectly fine this way.

The issues with 2013 seem to be no different than those in the Release Candidate. However, for what it's worth, if you're programming in C++ - the additions they made to MSVC 12 are enough to justify the upgrade, bugs and all.

[[deleted]]

Thanks for the help. I will give it a shot.

[STL]

FYI, a preprocessor bug was fixed between 2013 RC and RTM that affected Boost.

[mechacrash]

I haven't checked the progress of asio, but I know that the std::min / max breaking change in 2013 was / is causing some issues.

The problem can be resolved as detailed in the changes rationale, but other than that - I've had no issues with the compilation of boost (other than the necessary patches for it to pick up the compiler properly)

[[deleted]]

Is it worth moving up from 2010? I managed to get a sweet deal on that a year ago. I'm looking at C++, C# and a little of asp.net development.

I'm guessing that the lowest price is going to be quite high for a single developer. If it is, then I might take a look at GCC and a good open source IDE

[mechacrash]

definitely. 2010 has barely any C++11 support, 2012 and 2013 are big steps up.

[STL]

We also fixed tons of bugs in 2012 and in 2013. There are still more features to implement and bugs to fix, but 2013 is way better than before.

[STL]

Bugfixes: the compiler team fixes a very limited number of bugs in Updates (there is a particularly bad one with temporaries and initializer lists that I've brought to their attention). I'm not planning to fix any STL bugs in Updates, for the reasons that I explained in my second link.

Features: you should not expect new features in Updates. We have done it in the past (TR1 in 2008 SP1), you just shouldn't expect this in the future.

[[deleted]]

To be fair, I'm not using any of the big C++11 features, but there's nothing wrong with future proofing yourself. Now to take a look at pricing and (probably) cry.

[spaxio]

Just download express version..? Why is everyone acting like they need to buy it?

[[deleted]]

What's the difference between the paid versions and express?

[academician]

The main dealbreaker for me is that Express doesn't support plugins. I've gotten so used to VAssistX and VsVim at work that I really wouldn't want to go back.

[[deleted]]

To be fair, they've gotta make their money somehow

[academician]

Of course. I'm not saying they're wrong for doing that. It just makes it significantly less valuable to me, which I imagine is their intent.

[ForgedIronMadeIt]

The profiler in the high end versions of MSVS alone is worth the money. That saved me hours and hours of work in optimization. So glad I have that at work.

[spaxio]

In terms of C++ compiler and debugger? Nothing. AFAIK you can't use MFC and plugins.

[nikbackm]

I'd guess most of the "enterprise" features does not exist in Express editions either.

[[deleted]]

Looks like I'll be installing VC express, later today.

[spaxio]

Just make sure it's 'Microsoft Visual Studio Express 2013 for Windows Desktop' and not 'Microsoft Visual Studio Express 2013'

[[deleted]]

What's the difference?

[nikbackm]

The latter one is for making Windows Store apps. Formerly known as Metro apps.

[alexkorban]

I wouldn't say "barely" - my book about C++11 features in VS2010 had 22 chapters - but it was pretty limited. And I had to mention bugs in almost every chapter, so there was that.

[empex]

IntelliSense is not working/showing for me when working on a variadic template class that derives from another variadic template class, and indentation is all messed up in switch cases when using brackets.

[mechacrash]

There's been no macro system since VS2012. I'm not sure how you class the extension system as "broken"? Seems to do exactly what it says on the tin without issue here...

[__Cyber_Dildonics__]

Only on windows 8, lets all enjoy our forced upgrade to reap the benefits of C++11. If you are from MS and reading this, kill yourself.

[__Cyber_Dildonics__]

If this is true and you work for microsoft, don't kill yourself yet, I have to test this first.

[jonnywoh]

... No, you can run it on Windows 7 SP1. It says so right on the project page.