v1.8.5

Spin/Pasm for P1 ONLY - Outline/Semantic update

Minor Semantic/Outline fixes for P1

• Repair parsing of PUB/PRI method names (fix distraction by comment content)
• Repair parsing of object constants being used as array length specification
• Repair double-entries of PUB/PRI names in the P1 Outline

- Known Issues w/v1.8.5

Nothing really changed. Here's the recap.

• 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!!!!

Full Changelog: v1.8.4...v1.8.5

v1.8.4

Spin/Pasm for P1 and P2 - Outline update

Minor Outline adjustments for P1 and P2

• Repair parsing of long(...) code -- recognize long when adjacent paren. (issue #14)
• Move global labels under their enclosing DAT section, creating a more descriptive outline hierarchy (issue #13)

- Known Issues w/v1.8.4

Nothing really changed. Here's the recap.

• 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!!!!
• I'm sure there are more issues... but this is continually getting better!

Full Changelog: v1.8.3...v1.8.4

v1.8.3

Spin/Pasm for P1 and P2 - Syntax/Semantic update

Minor Syntax/Semantic recognizer update - Adds help for porting p1 code to p2

• Syntax P1 & P2: Recognize nested {} and {{}} comments
• Semantic P2: if () missing after a method name (mark it as unknown - RED -> error)
  • NOTE: we can't do this for "object method calls" until we have a full language server. (It's coming!)
• Semantic P2: If () missing after a spin built-in method name (mark it as unknown - RED -> error)
• Semantic P2: Flag P1 specific variables, mnemonics, methods as RED -> error so we know what needs conversion to P2

- Known Issues w/v1.8.3

Nothing really changed. Here's the recap.

• 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!!!!

v1.8.2

Spin/Pasm for P1 and P2 - Outlining update

Minor Outline/Navigation update for P1

• Add global Pasm labels to outline
• This completes the delivery of showing Global Labels within the outline for both P1 and P2

- Known Issues w/v1.8.2

Nothing really changed. Here's the recap.

• 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!!!!

v1.8.1

Spin/Pasm for P1 and P2 - Outlining update

Minor Outline/Navigation update for P2

• Add global Pasm labels to outline

- Known Issues w/v1.8.1

Nothing really changed. Here's the recap.

• 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!!!!

v1.8.0

Spin/Pasm for P1 and P2 - Highlighting update

Add [optional] FlexSpin preprocessor support (P1 & P2), Repair semantic highlight (P2)

• Add a new extension setting to enable recognition of FlexSpin Preprocessor Directives (Default: disabled)
• Adds flagging of Preprocessor directive lines as unknown when FlexSpin support is not enabled
• Fix P2 recognition of RET directive in Pasm2
• Fix P2 recognition of built-in _set, _clr variables in Pasm2
• Fix P1 & P2 recognition of constants when assignment uses #> and <# operators

- Known Issues w/v1.7.8

Nothing really changed. Here's the recap.

• 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!!!!

v1.7.8

Spin/Pasm for P1 and P2 - Tabbing update

Minor tabbing update

• Ensure org, asm and end, endasm lines use PUB/PRI tabstops
• Deconflict "Tab" from "Tab to Autocomplete"
• Adjust auto-closing pairs behavior (dialing things in slowly)

- Known Issues w/v1.7.8

Nothing really changed. Here's the recap.

• 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!!!!

v1.7.7

Spin/Pasm for P1 and P2 - Tabbing update

Minor tabbing update

• end and endasm are now positioned using In-line Pasm tab stops
• Corrected delete (left/Right) behavior in Align edit mode
• Cursor now positions as expected after TAB / SHIFT+TAB (this didn't work before)

- Known Issues w/v1.7.7

This is now a smaller list. Here's the recap.

• 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!!!!

NOTE: this was originally published as v1.7.6 but it failed to code-sign so had to be released again under the next number. In the repo it is still tagged as v1.7.6

v1.7.5

Spin/Pasm for P1 and P2 - Highlighting update

Minor highlighting update

• Add offset color for local vs. global pasm labels
• Detect and Flag invalid local pasm label syntax version: pasm1 vs. pasm2
• Correct backspace behavior (no longer removes more than one character)

- Known Issues w/v1.7.5

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!!!!

v1.7.4

Spin/Pasm for P1 and P2 - Highlighting update

Minor highlighting update

• Constant declarations are now identified correctly
• Spin builtin methods are now identified so other themes can render them better

- Known Issues w/v1.7.4

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!!!!