This video and the related ACCU article are both great and really have given me a lot to think of on this topic, it has clarified a number of issues and questions I've had working with && in my own code. Thanks Scott for giving the talk and allowing it to be shown on Channel 9 for those of us who couldn't be at the even and thanks to Charles for capturing it and getting it posted for us!
Apr 30, 2012 at 8:34 PM
This is amazing, I have been toying around with a pet project that interacts with several REST/JSON based API's and seriously feeling the lack of a good library for this type of work in native c++. This is the type of effort that I've been looking forward to and I can't wait to start playing with it.
@Charles Good job on the solo mission man, this was a great ep!
Dec 06, 2011 at 7:06 AM
@Raanen:It's not that I take offense but "can't even imagine" is a figure of speech. The scope of windows/visual studio is much bigger than anything I've worked on and I know just how much work its been in my own projects to maintain backwards compatibility, sometimes its just time to draw the line in the sand.
Dec 06, 2011 at 1:20 AM
@JimSpringfield: Thanks for taking the time to stop by and give an explanation. I can't even imagine how much goes into building and supporting these new API's and at some point it's understandable that a line has to be drawn on how much backwards compatibility you can manage and still get the product finished on time.
As you mentioned you're not dropping support for VC10, that's the toolset you want to use to target XP. For the product I'm working on the current plan is to switch to a maintenance support around the time Windows 8 arrives (much as XP is already in maintenance support only). New product versions will target newer versions of Windows. I mean seriously at some point there has to be a transition and lets be honest, there really aren't a whole lot of new features in VC11 that can't already be found in libraries such as Boost. It makes sense transition now and the above plan is a fairly painless one.
@Raanen:You mention using LoadLibrary and make it sound like it's just going to take a few lines. How do you know that's all that's involved? If that really is the case then take a look again at what Jim said, specifically:
Note that sometimes, even if we don't officially support it, DLLs may load on an older OS or you may be able to statically link the CRT and avoid the new APIs or even implement your own version of the new API.
If using LoadLibrary or something along those lines is as simple as you say it is the above appears to me to be an invitation for you to make it happen. I'm interested to see if the above is possible and will be testing it myself, I will post back with any findings. Before you throw in the towel, especially for something you consider to be easy, lets try and see if there are working alternatives, albeit unofficially supported.
Dec 05, 2011 at 2:01 PM
You guys I understand the frustration here and while I don't exactly agree with everyone's logic on the matter I do think you guys deserve a technical answer on why XP is no longer supported. On the other-hand you've been asked more than once to keep on topic in these GoingNative threads, with that in mind I've opened up a forum post on the matter and also quoted Bernd from above as I think his is the most rational explanation of why XP support is still needed.
Charles, if the discussion gets moved there can you help us out and try and get someone to drop by and give a technical clarification for the decision? Thanks man, and keep up the great work on GoingNative.
Nov 29, 2011 at 6:27 PM
@felix9 I spent a good chunk of time earlier today on that same path (ASCII C '67') but the closest I came was adding the ascii C and + values (so "C" + "+") but that only got me to 110.
Great job to the winners!
Nov 28, 2011 at 2:36 PM
@felix9 That's a great answer man!
Nov 27, 2011 at 7:04 PM
@STL Thanks for the detailed explanation of the situation as well as a very simple workaround.
I'm inclined to agree with the decision to keep infinity=5 given how easy it is to regain previous functionality when needed.
Nov 25, 2011 at 12:01 AM
My guess for the $112 pricetag is C++ 11 and the month of the event, February (the 2nd month): 112
My other guess would be this is the first (of many) C++ events in 20(12): 112
Nov 24, 2011 at 5:15 PM
@Charles Don't listen to the naysayers man, there is so much new (good) C++ content to consume around here than anywhere else and I have a sneaking suspicion your enthusiasm is at the root of a lot of it.
I have registered for my seat for the show and I can't wait to get out there and meet all these great people who are putting it on!
@tgoodhew I'm loving Visual Studio 11 so far, I am running into an issue however that is making it difficult to port many of my existing projects over. While I understand variadic templates won't be making it into the initial release is there any chance that we can the current "infinity" for the faked variadic templates back to 10 from the current 5?
I ask because one particular dependency, googletest, makes use of tuples and currently breaks as it exceeds the limit of 5 elements (but does keep under the limit of 10).