Displaying 3 results from an estimated 3 matches for "bad_symbol".
Did you mean:
addsymbol
2016 Feb 09
3
[RFC] Error handling in LLVM libraries.
...or_code one can define arbitrary error categories.
The problem with error categories is that they're limited to static
groupings of kinds of errors, but the user might need dynamic information
to recover.
Consider someone who wants to use libObject to write an object-file repair
tool: A "bad_symbol" error code tells you what went wrong, but not where or
why, so it's not much use in attempting a fix. On the other hand
"bad_symbol { idx = 10 }" gives you enough information to pop up a dialog,
ask the user what the symbol at index 10 should be, then re-write that
symbol table...
2016 Feb 10
5
[RFC] Error handling in LLVM libraries.
...nce types (in the general sense -
references, pointers, etc.) in errors. Errors that would otherwise require
references should have their error-message stringified at the point of
creation.
> > Consider someone who wants to use libObject to write an object-file
repair
> > tool: A "bad_symbol" error code tells you what went wrong, but not
where or
> > why, so it's not much use in attempting a fix. On the other hand
"bad_symbol
> > { idx = 10 }" gives you enough information to pop up a dialog, ask the
user
> > what the symbol at index 10 should be, th...
2016 Feb 03
6
[RFC] Error handling in LLVM libraries.
Hi Mehdi,
> If you subclass a diagnostic right now, isn’t the RTTI information
available to the handler, which can then achieve the same dispatching /
custom handling per type of diagnostic?
> (I’m not advocating the diagnostic system, which I found less convenient
to use than what you are proposing)
I have to confess I haven't looked at the diagnostic classes closely. I'll
take a