On Thu, Jun 25, 2015 at 06:44:11PM +0100, Ian Jackson wrote:
> We introduce ERROR_ABORTED now, so that we can write code to handle
> it, and decreee that functions might return it, even though currently
> there is nowhere where this error is generated.
>
> While we're here, provide ERROR_NOTFOUND
We introduce ERROR_ABORTED now, so that we can write code to handle
it, and decreee that functions might return it, even though currently
there is nowhere where this error is generated.
While we're here, provide ERROR_NOTFOUND which will also be used
later, but only as part of the public API.
Sig
