diff options
author | Nat Goodspeed <nat@lindenlab.com> | 2016-08-05 14:02:12 -0400 |
---|---|---|
committer | Nat Goodspeed <nat@lindenlab.com> | 2016-08-05 14:02:12 -0400 |
commit | 65d608cdac701ab10f84bd8dc4a6c0be7eef26f1 (patch) | |
tree | 1ab7507c093c699e91160f721d71d8764e8350d9 | |
parent | f459c67faea4bfcbca8e88c6d8b66319b4b461aa (diff) |
MAINT-6584: Clarify LLKDUMessageError::flush() throwing exception.
-rw-r--r-- | indra/llkdu/llimagej2ckdu.cpp | 6 |
1 files changed, 6 insertions, 0 deletions
diff --git a/indra/llkdu/llimagej2ckdu.cpp b/indra/llkdu/llimagej2ckdu.cpp index 9347e51b85..2adb90320c 100644 --- a/indra/llkdu/llimagej2ckdu.cpp +++ b/indra/llkdu/llimagej2ckdu.cpp @@ -165,6 +165,12 @@ struct LLKDUMessageError : public LLKDUMessage // terminating handler→flush call." // So throwing an exception here isn't arbitrary: we MUST throw an // exception if we want to recover from a KDU error. + // Because this confused me: the above quote specifically refers to + // the kdu_error class, which is constructed internally within KDU at + // the point where a fatal error is discovered and reported. It is NOT + // talking about the kdu_message subclass passed to + // kdu_customize_errors(). Destroying this static object at program + // shutdown will NOT engage the behavior described above. if (end_of_message) { throw "KDU throwing an exception"; |