Really, everyone codes an error code for no error (ERR_OK), but normally we don't print it on screen, and it's normally error code 0 or some such.
It is worrying that in their system they have 31,016,935 possible error states. That is probably some sort of tree, with lots of space holders for unassigned errors. Still impressive.
It probably meant something like "No error message matching this error code was found.". Lousy message for a pretty common problem in muti-lingual systems, where error messages are stored outside the program itself. The error code in question might even be generated because the error message file was not found...
Okay smarty pants, how did you generate that one?
ReplyDeleteReally, everyone codes an error code for no error (ERR_OK), but normally we don't print it on screen, and it's normally error code 0 or some such.
It is worrying that in their system they have 31,016,935 possible error states. That is probably some sort of tree, with lots of space holders for unassigned errors. Still impressive.
I just love software that tells you the wrong thing.
It probably meant something like "No error message matching this error code was found.". Lousy message for a pretty common problem in muti-lingual systems, where error messages are stored outside the program itself. The error code in question might even be generated because the error message file was not found...
ReplyDelete