| [cdt-dev] Error Parser Issues.. |
Hi,
I have submitted three Bugzilla reports regarding error parser issues. I would like to discuss these at the next CDT monthly meeting with the goal of reaching closure on the desired fixes to the issues.
-----
Bugzilla #65576:
The GNU error parsers never return TRUE. We believe that error parsers should return TRUE when they handle the error line and that the remaining error parsers on the list should not be called for that line. If there is functionality using the error parser list that needs to always be called for each line (does anyone know of any?), it should be using a different mechanism.
Bugzilla #66762: Issue with Error Parser ordering.
There are two things here.
i) CDT does not invoke the error parsers in user specified order.
ii) CDT dynamically changes the Error Parser order. CDT may be doing for performance reasons. Additionally, if desired, we could add an "Enable Error Parser Ordering" check box to the "generic" error parser picker dialog box. When true (the default), the Up and Down buttons would be active at the appropriate times (as they are today), and the error parser manager would respect the specified order. When false, the Up and Down buttons would be disabled and the error parser manager would be free to re-order the error parsers.
Bugzilla #66808: "Restore Defaults" button in Error Parser window of a Project property page does not work as expected.
In error parser window, user can select/unselect the error parsers, change the order of error parsers. For each "Build Target" configuration, there is a default set of Error Parsers included. For example, if user wants to build his/her project with Gnu C Compiler, the default error parsers are
i) CDT GNU C/C++ Error Parser
ii) CDT GNU Assembler Error Parser
iii) CDT GNU Linker Error Parser
iv) CDT Make Error Parser
When user presses the "Restore Defaults" button in error parser window of project property page, it is not restoring the default error parser list, instead, it is discarding the changes and setting to previous saved state that may not be default state always.
-----
Thanks & Regards,
Sunil.