Standardize "exception" status words #17
Description
I've been doing a lot of:
THROW(EXCEPTION);
Rather than throwing a status word that could give the user or host process useful feedback. This was mainly due to an early lack of fully understanding the device communication cycle.
But now it's time to standardize and document the exception-state status words and actually use them in the code.
See also
Related to this is issue #15 "Why aren't exceptions being caught?".