Re: [Monotone-devel] On E()s and N()s

[Markus Wanner]

Hi,

Thomas Keller wrote:
> So what I'd propose here is that actually distinguish between these two,
> and this could be as easy as creating a new naughty_failure class which
> extends from informative_failure and throw an instance of this instead
> the former in sanity.cc's sanity::naughty_failure. I'd also change the
> what() getter to add the "misuse: " part of the naugthy failure on call
> time and allow the return of the raw error without that prefix. Now the
> rest of the code should just continue to work because
> informative_failures are already catched and handled everywhere, and the
> naughty_failure exception could (especially) be catched for automate
> stdio and lead to a new error number within the stream context there.

This sounds fine from here (without remembering the different exception
classes in detail, though).

Regards

Markus Wanner