v1.7.2

Spin/Pasm for P1 and P2 - Highlighting Update

Update Spin highlighting (syntax and/or semantic parser fixes)

• Spin: Recognize label or data declaration on the DAT line
• Spin: Recognize non-float decimal numbers with exponents

Update Spin2 highlighting (syntax and/or semantic parser fixes)

• Spin2: Recognize label or data declaration on DAT line
• Spin2: Recognize non-float decimal numbers with exponents
• Spin2: Recognize debug_main and debug_coginit compile time directives
• Spin2: Recognize event names in pasm2 correctly
• Spin2: Fix cases where debug used without parenthesis causes the extension to crash
• Spin2: Recognize coginit constants (some pasm2 cases were being missed)
• Spin2: Add recognition of LutColors directive in debug statements with run-time terminal assignment
• Spin2: Recognize modcz operand constants

- Known Issues w/v1.7.2

Nothing has changed here. Here's the recap.

• We haven't yet learned how to control the ending position of the edit cursor. So in many cases when using selection not an insert point the cursor may end up not being where you might expect it to be after pressing TAB or Shift+TAB. We are looking into how to solve this. Even tho' this problem exists the formatting ability this new service provides is well worth this minor headache. We will keep looking for a means to get this under control.
• The single-quote comment (now only on debug statements) is being handled by the semantic (vs. syntactic) parser this is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within trailing line comments on debug lines
• Syntax highlight of DAT section sometimes fails... (although it is less often now...)
• Semantic highlight: the 'modification' attribute is being over-applied, should use more than := as test!!!!

We wish to thank Jay B. Harlow for his contribution to this new feature!

Thank you, Jay, your work is much appreciated!