Dear Bjorn,
This does not have any other use case than C and COM-Style API
interoperability: both `out_ptr` and `inout_ptr` and streamlined interfaces
purely for this purpose and to make writing against such APIs more
pleasant, more performant, and (most of all) more developer-time scale-able
than alternative approaches such as wrapping all such initialization-style
functions in C++-isms.
Sincerely,
JeanHeyd
On Mon, Jul 2, 2018 at 6:20 PM, Bjorn Reese via Boost wrote: On 06/28/18 21:03, ThePhD via Boost wrote: out_ptr is a small abstraction for making types such as std::unique_ptr, std::shared_ptr, boost::shared_ptr, and the upcoming
std::retain_ptr
http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2016/p0468r0.html
work
work C-Style output functions as a parameter, addressing the need of
wanting to be able to do "my_c_api_init( foo, bar, &my_smart_ptr );". It's Does out_ptr have other use-cases than C interoperability? _______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman
/listinfo.cgi/boost