[Lldb-commits] [PATCH] D29359: Start breaking some dependencies in lldbUtility
Zachary Turner via lldb-commits
lldb-commits at lists.llvm.org
Tue Jan 31 17:32:50 PST 2017
llvm::Error only enforces checking at the point that it goes out of scope.
So the example you mention should be supported, as long as you propagate
the value all the way up and don't destroy it. There's also ways to
explicitly ignore an Error (similar to casting to void to make the compiler
not warn about unused variables), so as a last resort we could put code
like that in the SB implementation if we had to
On Tue, Jan 31, 2017 at 5:23 PM Jim Ingham <jingham at apple.com> wrote:
> I think we discussed this before, but we need an informational error
> object. IIRC, the llvm::Error has to be checked. But for instance if you
> ask a value object to evaluate itself, but you've moved to a section of
> code where the variable has no location, then evaluating that value will
> result in an error. But that isn't an error the value object code needs to
> do anything about. And it might go all the way up through the SB & Python
> API's before it's appropriate to check the error.
> IIRC, the llvm::Error is one of those "you have to check it or you get
> smacked by the compiler" dealies. That's appropriate for some of our uses
> of Error, but not all.
> > On Jan 31, 2017, at 4:01 PM, Zachary Turner via Phabricator via
> lldb-commits <lldb-commits at lists.llvm.org> wrote:
> > zturner added a comment.
> >> Move Error from Core -> Utility
> > Also, I almost forgot.
> > Long term: Delete and use `llvm::Error`
> > https://reviews.llvm.org/D29359
> > _______________________________________________
> > lldb-commits mailing list
> > lldb-commits at lists.llvm.org
> > http://lists.llvm.org/cgi-bin/mailman/listinfo/lldb-commits
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the lldb-commits