cppcheck/addons/test/misra/misra_rules_multiple_lines.txt

Appendix A Summary of guidelines

Rule 1.1
Multiple
lines
text.
Rule 1.2
Multiple lines
text.
Rule 1.3 Required
Multiple
lines
text.
Rule 1.4
Should
Starts from lowercase letter.
Rule 1.5
Should
 starts from lowercase letter.
Rule 1.6
Can

contain empty lines.
misra.py: Fix up and improve load rules parser. (#1895) * misra.py: Fixup load rules parser. * misra.py: Report when rule text is missing in rule-texts file * misra.py: Allow to skip misra checks not specified in rule-texts. * misra.py: Remove top-level control flow. Create separate class that stores settings, instead of global variables. This is required to perform imports from misra.py for testing purposes. * misra.py: Add simple pytest test for load rules. * misra.py: Add document structure tests. * misra.py: Exit after show rules table. * misra.py: Add document structure tests. * misra.py: Fixup import pitfall with python2 * misra.py: Minor fixes 2019-06-17 21:17:29 +02:00			`Appendix A Summary of guidelines`

			`Rule 1.1`
			`Multiple`
			`lines`
			`text.`
			`Rule 1.2`
			`Multiple lines`
			`text.`
			`Rule 1.3 Required`
			`Multiple`
			`lines`
			`text.`
			`Rule 1.4`
			`Should`
			`Starts from lowercase letter.`
			`Rule 1.5`
			`Should`
			`starts from lowercase letter.`
			`Rule 1.6`
Loosen restrictions on MISRA rules text structure (#2157) Version 1.88 changed the parsing of the MISRA rules file adding a severity setting. This caused a regression in rule parsing. In particular the following format used to parse cleanly and produce rule output that would show the severity as part of the rule text. Rule 1.2 Advisory Rule text goes here. Rule 1.3 Required More rule text goes here. As of 1.88 a file structured like above would parse as having no rules. The problem is the use of blank lines as a rule delimiter. The modified rule parser wants to see a rules formatted like below: Rule 3.1 Required R3.1 text. Rule 4.1 Required R4.1 text. or: Rule 1.1 Add this rule and parse to next, skipping empty lines. Rule 1.2 Rule text. Any rule text that did not fall into one of the above formats would result in incomplete rule text parsing. Change the parsing of the rule text file so that blank lines are ignored instead of treating them as a delimiter between rules. Instead use the start of the next rule as a delimiter for the end of the previous rule. This allows both of the newer formats but also supports the behavior of pre-1.88 versions. Change units tests that were specifically forbidding the use of blank lines to ones that allow blank lines. 2019-09-09 21:43:44 +02:00			`Can`
misra.py: Fix up and improve load rules parser. (#1895) * misra.py: Fixup load rules parser. * misra.py: Report when rule text is missing in rule-texts file * misra.py: Allow to skip misra checks not specified in rule-texts. * misra.py: Remove top-level control flow. Create separate class that stores settings, instead of global variables. This is required to perform imports from misra.py for testing purposes. * misra.py: Add simple pytest test for load rules. * misra.py: Add document structure tests. * misra.py: Exit after show rules table. * misra.py: Add document structure tests. * misra.py: Fixup import pitfall with python2 * misra.py: Minor fixes 2019-06-17 21:17:29 +02:00
Loosen restrictions on MISRA rules text structure (#2157) Version 1.88 changed the parsing of the MISRA rules file adding a severity setting. This caused a regression in rule parsing. In particular the following format used to parse cleanly and produce rule output that would show the severity as part of the rule text. Rule 1.2 Advisory Rule text goes here. Rule 1.3 Required More rule text goes here. As of 1.88 a file structured like above would parse as having no rules. The problem is the use of blank lines as a rule delimiter. The modified rule parser wants to see a rules formatted like below: Rule 3.1 Required R3.1 text. Rule 4.1 Required R4.1 text. or: Rule 1.1 Add this rule and parse to next, skipping empty lines. Rule 1.2 Rule text. Any rule text that did not fall into one of the above formats would result in incomplete rule text parsing. Change the parsing of the rule text file so that blank lines are ignored instead of treating them as a delimiter between rules. Instead use the start of the next rule as a delimiter for the end of the previous rule. This allows both of the newer formats but also supports the behavior of pre-1.88 versions. Change units tests that were specifically forbidding the use of blank lines to ones that allow blank lines. 2019-09-09 21:43:44 +02:00			`contain empty lines.`
misra.py: Fix up and improve load rules parser. (#1895) * misra.py: Fixup load rules parser. * misra.py: Report when rule text is missing in rule-texts file * misra.py: Allow to skip misra checks not specified in rule-texts. * misra.py: Remove top-level control flow. Create separate class that stores settings, instead of global variables. This is required to perform imports from misra.py for testing purposes. * misra.py: Add simple pytest test for load rules. * misra.py: Add document structure tests. * misra.py: Exit after show rules table. * misra.py: Add document structure tests. * misra.py: Fixup import pitfall with python2 * misra.py: Minor fixes 2019-06-17 21:17:29 +02:00