search for: some_filesystem_operation

...when you need to produce early-exit code flows. A note about error objects: you should always have a variable and/or type name here. This gives you the opportunity to make it perfectly unambiguous whether it was an error or success. The example I give is std::error_code: if (std::error_code ec = some_filesystem_operation(...)) { /* unambiguously have an error code, because the condition was on the error code, not the function */ } -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.llvm.org/pipermail/llvm-dev/attachments/20130924/7f2d5c1f/attachment.html>

On Tue, Sep 24, 2013 at 4:17 PM, Nick Kledzik <kledzik at apple.com> wrote: > > On Sep 24, 2013, at 12:40 PM, Michael Spencer <bigcheesegs at gmail.com> > wrote: > > On Tue, Sep 24, 2013 at 12:33 PM, Rui Ueyama <ruiu at google.com> wrote: > >> Hi LLD developers, >> >> I'm about to make a change to invert the return value of Driver::parse()

On Sep 24, 2013, at 12:40 PM, Michael Spencer <bigcheesegs at gmail.com> wrote: > On Tue, Sep 24, 2013 at 12:33 PM, Rui Ueyama <ruiu at google.com> wrote: > Hi LLD developers, > > I'm about to make a change to invert the return value of Driver::parse() to return true on success. Currently it returns false on success. > > In many other functions, we return true