I hope XPCOM does not turn into an MSCOM clone.
<rant>
OLEDB is a fine example of an over-engineered interface
model. That's why everyone uses ADO instead.
</rant>
However, I would like to see a bare-minimum error reporting
interface that will give me a text description of the error suitable
for presenting to the user. The only thing I don't like about
having a "retrieve-info-on-last-error" is it does not cope
with re-entrancy very well. As for a nested error reporting
mechanism, I would discourage people from returning an
error message equivalent to "A error occurred at a lower
level." If you can't contribute something meaningful to the
error stack - leave it alone!
Regards,
Rick
Neil Hodgson wrote:
> Mark Hammond:
>
> If you want to copy MSCOM, why not go the whole way and add OLE DB style
> error information. These are the IErrorRecords and IErrorLookup interfaces.
> The purpose of IErrorRecords is to provide a stack of error information.
> Being able to find out not just the top level failure but the details is
> very useful. Java supports nested errors for the same reason. IErrorLookup
> allows lazy retrieval of error strings, help text etc. which reduces the
> cost of making this information available.
>
> Neil
