search for: r217791

Hello everyone, I bring to discussion the necessity/design of a new type of smart pointer. r215176 and r217791 rise the problem, D5443 <http://reviews.llvm.org/D5443> is devoted to the solution. r215176 applies several temporary ugly fixes of memory leaks in TGParser.cpp which would be great to be refactored using smart pointers. D5443 <http://reviews.llvm.org/D5443> demonstrates how the solu...

On Wed, Sep 24, 2014 at 7:50 PM, Justin Bogner <mail at justinbogner.com> wrote: > Anton Yartsev <anton.yartsev at gmail.com> writes: > > Hello everyone, > > > > I bring to discussion the necessity/design of a new type of smart > pointer. > > r215176 and r217791 rise the problem, D5443 is devoted to the solution. > > r215176 applies several temporary ugly fixes of memory leaks in > TGParser.cpp > > which would be great to be refactored using smart pointers. D5443 > demonstrates > > how the solution with a certain type of smart point...

...actored in the more easy and safe way. > > Attached is a proposed interface/implementation. > Any ideas, suggestions? Is it OK to move forward with the solution? > > Hello everyone, > > I bring to discussion the necessity/design of a new type of smart pointer. > r215176 and r217791 rise the problem, D5443 > <http://reviews.llvm.org/D5443> is devoted to the solution. > r215176 applies several temporary ugly fixes of memory leaks in TGParser.cpp > which would be great to be refactored using smart pointers. D5443 > <http://reviews.llvm.org/D5443> demonstr...