|
|
|
|
|
by meibo
1596 days ago
|
|
I've had good experiences with "error codes". In our case, we came up with a way to assign unique codes to standard library exceptions for the language we use(.NET), custom codes for our own exceptions, and mask that with a number that roughly indicates where the exception occurred. You end up getting codes like 0x800482c6 though which might end up frustrating users, since they have no real way to decode them. |
|