When discussing the Python interface in issue757, we decided to move error-checking code that checks that the options passed to a component are consistent, into those components (for example checking that lists are non-empty, etc.). To still report the errors in the context in which they occurred, we want to throw an exception for errors and catch it in the calling code of the parser. We currently have two places where we generate warnings during parsing. If the change means that we can no longer generate them, we'll drop the possibility to generate warnings altogether. (The current warnings are not that important and we have similar places that do not generate warnings.)
The point of this is that if components are created without the parser (e.g., with the Python interface), they should also check those errors.
|