Voit lisätä twiitteihisi sijainnin, esimerkiksi kaupungin tai tarkemman paikan, verkosta ja kolmannen osapuolen sovellusten kautta. Halutessasi voit poistaa twiittisi sijaintihistorian myöhemmin. Lue lisää
@VisualStudio I know some of your devs are all about using emulators as test cases, so can I ask on behalf of us at @mamedev_org why you haven't adopted MAME has a standard test case yet? It's hit C++1x, template, and ICE bugs left and right since late in the VS2017 cycle.
Take, for example, this bug report, which originated from issues compiling MAME: https://developercommunity.visualstudio.com/content/problem/630838/vs2019-v1614-error-with-comparison-operator-in-c-c.html … Or any number of the workarounds visible in our Github history that we've had to implement to maintain MSVC compatibility.
I don't at all intend to detract from projects like @Dolphin_Emu, but it's a little insulting that it's rumored that projects like that are apparently in your standard test suite, yet we've had no end of trouble compiling with MSVC for literally years, and mum's the word.
I'm bordering on a rant here, but especially considering that venerable Microsofties and ex-MSFTies like @aaronsgiles are or have been part of the MAME project, why the reticence?
Then don't use MSVC? There are so many GCC implementations for Windoze, MinGW is just one of them.
Oh, thank you Captain Obvious of the USS Apparent, MinGW is actually the official supported toolchain on Windows for @mamedev_org, but I actually like MSVC's debugger. Screw me, right?
It goes back to the VCMAME days. Here's a visual studio ICE from 2005 that I started a thread about on the MSDN forums... https://social.msdn.microsoft.com/Forums/vstudio/en-US/29c9c968-6ddc-4217-844a-5f50afe5d8c1 …
Twitter saattaa olla ruuhkautunut tai ongelma on muuten hetkellinen. Yritä uudelleen tai käy Twitterin tilasivulla saadaksesi lisätietoja.
