search for: checkederror

Hi Rafael, > The main thing I like about the diagnostic system is that it lets us > differentiate two related but independent concepts: > > * Giving the human using the program diagnostics about what went wrong. > * Propagating an error to the caller so that the upper library layer > can handle it or pass it up the stack. I don't think these are really independent. Whether

...yself and Kevin Enderby are signing up to weave this through libObject and the JIT. Other libraries could be converted as people see fit, with ECError providing an interface between the std::error_code world and TypedError. > Given that I would > suggest going the more incremental way. Add a CheckedError that wraps > error_code and use to make sure the errors are checked. When a better > diagnostic is needed, pass in a diagnostic handler. Our first use-case for this system is libObject, where we want to use this to enable richer error messages. An incremental approach would involve threading...