C++ and TR1
I've seen some posts to the fact that TR1 is not included in VC 2005. Is there a release where TR1 will be included (Orcas?, VC 2005 SP1?)
At the moment, one has to shell around $200 USD to get it from Dinkumware, or wait for the next release of Boost (1.34) to get an incomplete (but sufficient) implementation (smart pointers, regular expressions, etc) with the std::tr1 namespace in it.
Regards,
Javier
That is one of the the biggest problems I have with Microsoft's approach to Visual Studio.
In order to add a couple of include files one is expected to re-purchase a new version of the IDE.
Nikola Dudar - MSFT (old name) wrote: |
| However we are aware of this situation and inclusion of TR1 is going to be considered during feature prioritization for the release of Visual C++ after Orcas. Thanks, Nikola | |
After Orcas? by that time the next C++ standard revision (C++0x) will be published (expected in 2009) in which case the majority of TR1 will most likely be incorporated into C++0x, shouldn't you guys be worried/prepared for that otherwise Visual C++ will seriously lag behind (yet again).
I fail to see the severity of this problem, as long as Dinkumware and the publicly available Boost both have working implementations. IMHO I'd rather have the VC team work on implementing 0x, than to sidetrack (and spend precious time) re-implementing already public libs.
I would like tr1 included in Visual Studio ASAP.
While I like boost and dinkumware the policy here is that we should keep extern dependencies to a minimum. Also, its unmanageable to include boost in our source tree (that is the way the build system works here). While bcp helps its still 289 files, 46 folders just to use boost :: shared_ptr.
If I would be the boss here I would order boost on all developer machines but I'm not.
If std::tr1 was part of Visual Studio I could use shared_ptr<> and all developers would have it without installing an extra library on the machine or clutter the source tree with external dependencies.
It frustrates me that I have to implement my own smart pointers when I know there are good-quality coming in tr1. I would like the wait for tr1 in Visual studio to be as small as possible.