search for: error_category

...detail. 2. The only function defined in _do_message is specifically intended for system errors that report via errno, which is not what the custom categories are doing. As far as I can tell, the custom categories are only inheriting from _do_message is apparently to get around the fact that error_category's constructor is private, and that _do_message is a friend class of error_category. If we want to continue using error_code the way we currently are, I think the right thing to do here is to make error_category's constructor protected and stop inheriting from _do_message. Would anyone obj...

...AEAUsend_lambda@server_session@@PEBD3 at Z@4HA))​ ​ lld-link: warning: C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally defined symbol imported: _CxxThrowException (defined in libvcruntime.lib(throw.obj)) [LNK4217]​ lld-link: error: undefined symbol: "class boost::system::error_category const & __cdecl boost::system::detail::system_category_ncx(void)" (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ >>> referenced by C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class boost::system::error_category const &...

...nd get rid of the wrapper class. >> An other issue is that since llvm::error_code was designed to return a fixed set of strings, there is no way to return a dynamic error message (e.g. "relocation 27 is invalid"). > > I'm pretty sure that the linker can specify a custom error_category with whatever information you want, and then return an error_code put with that. Michael would know for sure, but it is definitely in the design of error_code for it to be extensible. >From what I can tell error_code is about wrapping out OS specific "int" error codes, and how to map...

...3 at Z@4HA))​ > ​ > lld-link: warning: > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally > defined symbol imported: _CxxThrowException (defined in > libvcruntime.lib(throw.obj)) [LNK4217]​ > lld-link: error: undefined symbol: "class > boost::system::error_category const & __cdecl > boost::system::detail::system_category_ncx(void)" > (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ >>>> referenced by > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class > boost::system::er...

...; lld-link: warning: > > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally > > defined symbol imported: _CxxThrowException (defined in > > libvcruntime.lib(throw.obj)) [LNK4217]​ > > lld-link: error: undefined symbol: "class > > boost::system::error_category const & __cdecl > > boost::system::detail::system_category_ncx(void)" > > (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ > >>>> referenced by > > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class &g...

...here, but does a returning an std::tuple work? > An other issue is that since llvm::error_code was designed to return a fixed set of strings, there is no way to return a dynamic error message (e.g. "relocation 27 is invalid"). I'm pretty sure that the linker can specify a custom error_category with whatever information you want, and then return an error_code put with that. Michael would know for sure, but it is definitely in the design of error_code for it to be extensible. > In asking around for clean models on how to do this better, I've heard two interesting ideas: > >...

...D3 at Z@4HA))​ > ​ > lld-link: warning: > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally > defined symbol imported: _CxxThrowException (defined in > libvcruntime.lib(throw.obj)) [LNK4217]​ > lld-link: error: undefined symbol: "class > boost::system::error_category const & __cdecl > boost::system::detail::system_category_ncx(void)" > (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ >>>> referenced by > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class > boost::system::er...

...the wrapper class. > >>> An other issue is that since llvm::error_code was designed to return a fixed set of strings, there is no way to return a dynamic error message (e.g. "relocation 27 is invalid"). >> >> I'm pretty sure that the linker can specify a custom error_category with whatever information you want, and then return an error_code put with that.  Michael would know for sure, but it is definitely in the design of error_code for it to be extensible. > > >From what I can tell error_code is about wrapping out OS specific "int" error codes, and h...

...D3 at Z@4HA))​ > ​ > lld-link: warning: > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally > defined symbol imported: _CxxThrowException (defined in > libvcruntime.lib(throw.obj)) [LNK4217]​ > lld-link: error: undefined symbol: "class > boost::system::error_category const & __cdecl > boost::system::detail::system_category_ncx(void)" > (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ >>>> referenced by > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class > boost::system::er...

...h, that is annoying. >>> An other issue is that since llvm::error_code was designed to return a fixed set of strings, there is no way to return a dynamic error message (e.g. "relocation 27 is invalid"). >> >> I'm pretty sure that the linker can specify a custom error_category with whatever information you want, and then return an error_code put with that. Michael would know for sure, but it is definitely in the design of error_code for it to be extensible. > > From what I can tell error_code is about wrapping out OS specific "int" error codes, and how...

I already mentioned what flag I tried. It's in the first email in this thread. And I want to link against Boost.System and the Jinja2Cpp library (the latter's documentation can be found here: https://github.com/flexferrum/Jinja2Cpp . And I also have some GUI applications using FLTK as well that I want to try to build using LLVM as well, so I'll have to know how to link against

...D3 at Z@4HA))​ > ​ > lld-link: warning: > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o: locally > defined symbol imported: _CxxThrowException (defined in > libvcruntime.lib(throw.obj)) [LNK4217]​ > lld-link: error: undefined symbol: "class > boost::system::error_category const & __cdecl > boost::system::detail::system_category_ncx(void)" > (?system_category_ncx at detail@system at boost@@YAAEBVerror_category at 23@XZ)​ >>>> referenced by > C:\Users\Osman\AppData\Local\Temp\currency_converter-264ae1.o:("class > boost::system::er...

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 object ownership. The Reader class currently has an interface that can be simplified down to: virtual error_code

...wrapper class. > > >> An other issue is that since llvm::error_code was designed to return a fixed set of strings, there is no way to return a dynamic error message (e.g. "relocation 27 is invalid"). > > > > I'm pretty sure that the linker can specify a custom error_category with whatever information you want, and then return an error_code put with that. Michael would know for sure, but it is definitely in the design of error_code for it to be extensible. > > >From what I can tell error_code is about wrapping out OS specific "int" error codes, and h...

...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. > > s...

On Tue, Apr 4, 2017 at 12:36 PM, Duncan P. N. Exon Smith < dexonsmith at apple.com> wrote: > > On 2017-Apr-04, at 12:12, Peter Collingbourne <peter at pcc.me.uk> wrote: > > On Mon, Apr 3, 2017 at 8:13 PM, Mehdi Amini <mehdi.amini at apple.com> wrote: > >> >> On Apr 3, 2017, at 7:08 PM, Peter Collingbourne <peter at pcc.me.uk> wrote: >>