QDLException used to be a general purpose exception. It and its subclasses have mutated so that they now track parser information, line numbers and other information so a good report on failures can be created. User defined modules to extend QDL should never use this. A few older ones do and should just be amended to be in line with current best practices. These are benign in the sense that nothing really bad happens, just the error reports are really squirelly.
QDLException used to be a general purpose exception. It and its subclasses have mutated so that they now track parser information, line numbers and other information so a good report on failures can be created. User defined modules to extend QDL should never use this. A few older ones do and should just be amended to be in line with current best practices. These are benign in the sense that nothing really bad happens, just the error reports are really squirelly.