Re: shared_ptr



P.J. Plauger wrote:
"LarryW" <lwdaddio@xxxxxxxxxxxxxxxxx> wrote in message
news:VA.00000024.101f5ba6@xxxxxxxxxxxxxxxxxxxx

In article <Q8idnWgiP9smVDLYnZ2dnUVZ_vWtnZ2d@xxxxxxxxxxxx>, P.J.
Plauger wrote:
As of the Berlin meeting last April, the C++ committee voted
to incorporate most of TR1 (including shared_ptr) into the next
revision of Standard C++. You can get all that stuff now by
licensing our upgrade library for VC++ and layering it atop the
shipped library. We're still trying to convince Microsoft to license our
TR1 code
sooner rather than later, instead of waiting several years for it
to become a formal part of the new C++ Standard. Microsoft is very
much driven by perceived customer demands. If you want it, let 'em
know.
I didn't get it from the Boost library because I didn't want the
hassle of trying to get it layered on all of our developers
installs. I want something
like that to be a built in thing. How would you suggest is the best
way to
"let 'em know"? Thanks!

I defer to the MVPs to tell you the best channel to get Microsoft's
attention.

Post a suggestion on Connect, and post a link to it here so others who find
this thread can vote on it.

http://connect.microsoft.com/feedback/?SiteID=210

-cd


.



Relevant Pages

  • Re: shared_ptr
    ... You can get all that stuff now by licensing our upgrade ... We're still trying to convince Microsoft to license our TR1 code sooner ... formal part of the new C++ Standard. ...
    (microsoft.public.vc.language)
  • Re: shared_ptr
    ... You can get all that stuff now by licensing our upgrade ... We're still trying to convince Microsoft to license our TR1 code sooner ... formal part of the new C++ Standard. ...
    (microsoft.public.vc.language)
  • Re: shared_ptr
    ... standard yet or not. ... to incorporate most of TR1 into the next revision ... You can get all that stuff now by licensing our upgrade ... We're still trying to convince Microsoft to license our TR1 code sooner ...
    (microsoft.public.vc.language)
  • Re: C++ standard committee censor different opinions
    ... I'd like to explain my position, because I don't think Bill Plauger has it ... C++ committee were ones that I had held for many years,. ... it's slightly inaccurate to say that I "proposed changes" to Standard ... same facts that I did and independently drew similar conclusions. ...
    (comp.lang.cpp)
  • Re: vector of char arrays
    ... > components will really become part of the standard and if so, ... > the appropriate namespace. ... > 'tr1' may be a macro defined by users. ...
    (comp.lang.cpp)