Tracking Parser Refactor

[Matthewar]

Starting with commit f8c0728ee7420eecbdc1c8e0f64905eccab145da - the parser is being refactored for better usability and complete testing before release.

Using this issue to track changes to the parser and add elements to be considered.

[Matthewar]

Using parsec to write parser in monadic style. Need to ensure that error messages - which are implemented in a different way, are carried across from previous method.

[Matthewar]

Potential errors to add:

• Invalid character occurred (VHDL only supports ASCII characters - at least in 1987)
  • Edit: Issue #53 is related
• Accidental end of string literal (single container rather than double in string literal)

[Matthewar]

Currently testing for error cases as well as valid cases, but not testing error messages, should probably check for the actual message to guarantee "readable" error messages.

[Matthewar]

Future consideration: How to process error recovery with parsec.

[Matthewar]

See issue #47

[Matthewar]

Need to clean generators file, to remove commented functions.

[Matthewar]

Will need to check this branch for any commented functions before merging (clean up any old functions not moved across but left in the code)