* Issue#1273: Added rules for_generate_statement_502 and iteration_scheme_502.
* Issue#1273: Added tests for rules for_generate_statement_502 and iteration_scheme_502.
* Issue#1273: Added documentation for rules for_generate_statement_502 and iteration_scheme_502.
* Issue#1271: Added rules null_statement_300 and null_statement_500.
* Issue#1271: Added tests for rules null_statement_300 and null_statement_500.
* Issue#1271: Added documentation for rules null_statement_300 and null_statement_500.
* Issue#1241: Added meta test that tests all token classifications available.
* Issue#1241: Added classification result for resolution indications.
* Issue#1241: Removed now-redundant test files.
* Issue#1241: Formatting update.
* Issue#1236: Improved LRM name list acquisition.
* Issue#1241: Updated class names for consistency.
* Issue#1241: Improved safety of automated test name generation.
* Issue#1241: Simplified function name.
* Issue#1241: Duplication reduction.
* Issue#1241: Efficiency improvement.
* Issue#1241: Refactored code to be more clean by using pathlib's features.
* Issue#1241: Formatting.
* Issue#1241: Delete tests/vhdlFile/test_bit_string_literal.py, which now duplicates test_token.py.
* Issue#1243: Updated external name classification_test_input.vhd to expose bug.
* Issue#1243: Updated classification_results.txt to match desired output
* Issue#1243: Updated external_signal_name.py to fix bug.
* Issue#1243: Updated external_variable_name.py to fix bug.
* Issue#1243: Updated external_constant_name.py to fix bug.
* Issue#1243: Fixed external_variable_name.py.
* Issue#1243: Minor simplification in external name classification
* Issue#1243: Minor simplification in external name classification
* Issue#1243: Minor simplification in external name classification
In current implementation the user see something like the following when
ClassifyError is raised:
Error: Unexpected token detected while parsing procedure_call_statement @ Line 49, Column 22 in file None
Expecting : ;
Found : )
In a project that contains multiple files, the user is clueless as he does not
know which of the files caused the error.
This change adds the name of the file to the message.
Error while processing xxx:
Error: Unexpected token detected while parsing procedure_call_statement @ Line 49, Column 22 in file None
Expecting : ;
Found : )
Signed-off-by: Alon Bar-Lev <alon.barlev@gmail.com>
* Issue#1212: Corrected order of operations in extract_pairs to ensure that it does not return an empty list as one of the pairs.
* Issue#1212: Updated the tests to exercise failure case that raised this isssue.
* Issue#1212: Updated extract_indexes_from_pairs to strip any empty pairs from the input list.
* Issue#1225: Corrected tool name in help message for vsg_rule_doc_gen.
* Issue#1225: Added path argument to vsg_rule_doc_gen.
* Issue#1225: Passed path argument to top-level function in vsg_rule_doc_gen.
* Issue#1225: Updated reserved_rules documentation.
* Issue#1225: Updated ieee_rules documentation.
* Issue#1225: Whitespace changes.
* Issue#1225: Simple test added for the main function in vsg_rule_doc_gen.
* Issue#1225: Whitespace changes to appease black formatter.
1) Implemented "phase" concept to help with implementing changes
a) Added phase attribute to rule class
b) Updated all rules to include a phase number
c) Top level program runs all rules in a particular phase first before going on to next phase.