TR1 support for Visual Studio 2005 by Jon Anglin

I wonder if people gets discouraged to comment because this item has been marked as Closed (Won't Fix), but I think that it merits a more deterministic response from Microsoft (like when it can be incorporated).

As I'm sure MS already knows, being an active participant in the C++ Standard through Herb Sutter (and possibly others), C++ 0x will hit the streets within two years, along with TR2, so my question to MS is really what are the plans for VC++ beyond Orcas in terms of standards compliance?

I, for one, would like to see this moved up in priority. It seems a shame to have to wait so long to catch up with the standards bodies - they're not reknowned for fast action in the first place, so there's really no excuse for not seeing these changes coming.

Thanks for submitting your feedback to us. We appreciate the time you have take to work with us to improve our product.

During sorting, this item was classified as a ‘suggestion’ or ‘design change request’. This classification implies that you are asking for an improvement to the product that falls outside its current specification. This might include asking for additional features, requesting that an existing feature work in a way that was not originally intended, asking for existing features to support or conform to additional platforms or standards, or asking for us make a breaking change to existing behaviour of the product. If you disagree with this classification, please reactivate this issue stating “Wrong classification” and explain why you think this report is really a bug.

After sorting, we reviewed all these issues to analyzed which were commonly requested by our customers. We also looked at which items fitted within the resources available for the current “Orcas” release. Unfortunately, we’ve determined that this issue is not of sufficient priority to work on during this release, or requires too many resources to implement given our available staffing and time.

At this time, we are resolving this issue as “won’t fix”, which means that we won’t be addressing this issue during our current product cycle. We looked at adding TR1 functionality for VC9. Though we do think there are some exciting additions in these libraries, we don't have the time to add them to the product at this time. Though Dinkumware does indeed have a TR1 implementation shipping, there is still substantial work on our end to add a library like this to our product, and we couldn't fit it into the tight schedule we have. We will definitely be revisiting TR1 in future versions.

If you disagree with this resolution please reactivate the issue stating “wrong priority” explaining why you think we’ve made a mistake in not addressing your issue.

Visual Studio we get several thousand customer suggestions each year. This volume makes it too expensive for us to hold on to this suggestion and reconsider it for our next product cycle. Also, because we implement hundreds of new features each year, your suggestion may not be completely relevant by the time our current product is completed. So this is the last communication you’ll see from us on this issue, unless you reactivate it for the reasons given above.

When we plan our next version, teams will review the highest priority of the “won’t fix” items from this list. Additionally, teams that work on longer-term plans for features that we will deliver after “Orcas” may already have incorporated aspects of this request in their planning. However, we’re not able discuss these longer-term features at this time.

We encourage you to take part in our Customer Technical Preview and ‘beta’ programs for our next version. Feedback from customers in response to these releases had a major impact on shipping VS 2005 and on planning for our next version. Your issue was read and reviewed by several team members. We appreciate you taking them time to help us build a better product.

Thanks for your help, and feel free to get in touch if you have questions or concerns.

Martyn Lovell (martynl@microsoft.com)
Development Lead
Visual C++ Libraries