101–110 of 201 posts
Earlier quoted context omitted.
The Windows kernel is C++. From what I've seen (shared source), it's mainly C-style C++ though. I didn't see a single template or a class in my travels.
If you read the WRK, ntoskrnl is all C...
And yet, still no formalized C99 support. I know everybody is hot and bothered about C++11, but honestly I'd suggest just getting proper support for things we've needed for a decade or so before chasing the new shiny.
Have you missed the news? C is dead on Microsoft tooling, they have deprecated it. http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and...
Earlier quoted context omitted.
ex-VS person here (from 5 years ago though). It is never an either-or. It is always a complex mix of what customers ask for, what the strategic priorities/market realities are. Often the problem with these queries is that there are not enough devs complaining to MSFT. No PM/engg manager is going to ignore a bug/problem if it shows up high in customer requests. On promotions - I think it's the reverse problem. People…
Mozilla has been fighting the MSVC linker's 3GB virtual address space limit for years. Mozilla has asked Microsoft for a 64-bit linker that can produce 32-bit code, but Microsoft apparently has no plans for such a configuration. https://groups.google.com/forum/?fromgroups#!topic/mozilla.d...
Earlier quoted context omitted.
This pisses me off, too. I really should patch the menu resource someday and change it to lowercase. I also don't understand that Microsoft violates its own HID guidelines; shouldn't they set a proper example?
Easier method: http://stackoverflow.com/questions/10859173/how-to-disable-a...
Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.
nobody is asking for yearly updates for Visual Studio Ahem... I am. I would much rather have smaller more frequent updates to important tools than huge disruptive ones. Short feedback loops are a good thing.
That's what service packs are for. With a product that has as big a footprint as Visual Studio it will be impossible for shops to keep up with the annual versions. Many will simply delay updates. Ironically, increasing the speed of major release may actually delay the introduction of some improvements by customers.
Yet another Visual Studio, yet another truckload of "features" that do nothing to help day-to-day, heavy-lifting programmers. (And which probably help by adding bugs or just bloating the system). Sigh. I am hoping they have made substantial improvements that are not mentioned in this blog post.
Earlier quoted context omitted.
Have you missed the news? C is dead on Microsoft tooling, they have deprecated it. http://herbsutter.com/2012/05/03/reader-qa-what-about-vc-and...
I prefer to think of it as "Microsoft tooling is dead", since C continues to work just fine.
Way way way way, WAY too soon Microsoft... most shops, including my current employer aren't even on 2012 yet... Honestly I prefer VS to be tied to desktop OS releases or SQL release or something other than yearly. This is not a Madden game, nobody is asking for yearly updates for Visual Studio.
Seriously! My company has been keeping up with the latest stuff but I have hard time understanding what the justification was behind releasing a whole new Visual Studio version. Are there new features that won't be available in VS 2012? I guess we'll see at the Build conference.
Earlier quoted context omitted.
Mozilla has been fighting the MSVC linker's 3GB virtual address space limit for years. Mozilla has asked Microsoft for a 64-bit linker that can produce 32-bit code, but Microsoft apparently has no plans for such a configuration. https://groups.google.com/forum/?fromgroups#!topic/mozilla.d...
What I want to know is how someone can see that their software project has become unlinkable on a 32-bit OS and somehow think that this is purely a compiler problem.
Mozilla has never struck me as the most... forward looking.