Displaying 3 results from an estimated 3 matches for "blah_reader_error_category".
2012 Jun 19
2
[LLVMdev] object construction patterns and unique_ptr
...e parsed.
>>
>> -Nick
>
> I believe that specifically for object file parsing errors a
> pair<error_code, vector<string> values> (or something similar) as a
> member of File would work. This would be used as:
>
> // In the error_category stuff
> class blah_reader_error_category : public llvm::_do_message {
> public:
> virtual std::string message(int ev) const {
> ...
> case uknown_reloc:
> return "uknown relocation % at %";
> ...
> }
> };
>
> // In the reader.
>
> setError(make_pair(blah_error::unkown_reloc,...
2012 Jun 18
0
[LLVMdev] object construction patterns and unique_ptr
...error_code with which file path could not be parsed.
>
> -Nick
I believe that specifically for object file parsing errors a
pair<error_code, vector<string> values> (or something similar) as a
member of File would work. This would be used as:
// In the error_category stuff
class blah_reader_error_category : public llvm::_do_message {
public:
virtual std::string message(int ev) const {
...
case uknown_reloc:
return "uknown relocation % at %";
...
}
};
// In the reader.
setError(make_pair(blah_error::unkown_reloc,
vector<string>{relocationumer, loc})); // loc co...
2012 Jun 18
6
[LLVMdev] object construction patterns and unique_ptr
On Jun 16, 2012, at 3:51 PM, Chris Lattner wrote:
> On Jun 15, 2012, at 3:48 PM, Nick Kledzik wrote:
>
>> In lld we have a Reader class which is a factory that takes .o file(s) and produces an in memory lld::File object(s). But in doing so, there could be I/O errors (file not readable) or file may be malformed. We are also using C++11 in lld, so we use std::unique_ptr for managing