v1.3.7

Miscellaneous semantic highlight fixes

• Fix highlighting of multiple same-name constants in con declaration
• Fix highlighting of built-in variable and method names in debug() statements
• Fix highlighting of constant names in case statements with a constant range as match case
• Fix highlighting of org constant name as the offset
• Fix highlighting of constant names in complex constant assignment

Known Issues w/v1.3.6

• Sadly, The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We don't have a fix for this yet.
• 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...

v1.3.6

Improve debug() highlight methods and named operators correctly - misc fixes

• NEW single-quote comments on section name (DAT, VAR, OBJ, and CON) lines now show up in the outline (was just brace comments)
• Now highlights method names and named operators within debug statements
• Improved number, number-base recognition
• Improved highlighting of array sizes when multiple arrays are declared on a single line
• Improved highlighting of array-of-objects declaration
• Finally addresses the "Occasional issues with highlighting of enum leading constant"

Known Issues w/v1.3.6

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We don't have a fix for this yet.
• 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...

v1.3.5

Improve debug() single quote string parsing and misc. fixes

• Don't flag keywords within single quote strings
• Recognize float operators in more locations
• Recognize debug methods in a more correct manner

Known Issues w/v1.3.5

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We don't have a fix for this yet.
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.3.4

Improve debug()-display Highlight for new style with single-quoted strings

• Fix case where there are multiple `() sets in one string

Known Issues w/v1.3.4

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We don't have a fix for this yet.
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.3.2

Improve debug()-display Highlight for older style with double-quoted strings

• Fix highlighting of debug() statements containing double-quoted strings
• Fix object references in DAT-PASM and debug() statements containing double-quoted strings
• Fix highlight of comments starting with '' (two single-quotes)

Known Issues w/v1.3.2

• The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We have don't have a fix for this yet.
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.3.1

Finish debug()-display Highlight and Validation

• Adds new directive support for validating debug() display lines that use runtime display names
• Fix highlighting of debug() statements within in-line pasm
• Fix label on ORG directive
• Fix highlighting of ORGH directive

NOTEs v1.3.1

• this adds support for the new Spin2 Extension directive:
  • {-* VSCode-Spin2: nextline debug()-display: {displayType} *-}
  • Where: {displayType} should be one of [Logic, Scope, Scope_XY, FFT, Spectro, Plot, Term, Bitmap, and Midi]
• The following runtime forms can now be handled by preceeding them with this new directive:
  • debug(`zstr_(displayName) lutcolors `uhex_long_array_(image_address, lut_size))
  • debug(`lstr_(displayName, len) lutcolors `uhex_long_array_(image_address, lut_size))
  • debug(`#(letter) lutcolors `uhex_long_array_(image_address, lut_size))

Known Issues w/v1.3.1

• Sadly, The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We have don't have a fix for this yet.
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.3.0

Initial Release of debug()-display Highlight and Validation

• Adds initial highlighting support for all debug() displays (Logic, Scope, Scope_XY, FFT, Spectro, Plot, Term, Bitmap, and Midi)
• Unique colors within debug statement for displayType, displayName, keywords, and colors
• Validation: When a keyword is not legal for the display or is spelled incorrectly then is colored bright red
• Moved single comment out of syntax into semantic highlighting so we can have single-quoted strings in our debug statements. (Syntax highlighting is not context-aware, so entire tail of a debug() statement was incorectly rendered as a comment)

Initial limitations

• The runtime calulation of display name is not supported, yet. (In an upcoming release you'll be able to specify the preferred display type for validation of each of these statements.)
• The following example runtime forms will be handled by the new directive when released:
  • debug(`zstr_(displayName) lutcolors `uhex_long_array_(image_address, lut_size))
  • debug(`lstr_(displayName, len) lutcolors `uhex_long_array_(image_address, lut_size))
  • debug(`#(letter) lutcolors `uhex_long_array_(image_address, lut_size))

Known Issues w/v1.3.0

• Sadly, The single-quote comment now being handled as semantic (vs. syntactic) is causing external VSCode extensions to do brace, parenthesis, and bracket paring to be marked within our trailing line comments. We have don't have a fix for this yet.
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.2.3

Minor Highlighting Update

• Repair highlighting of float operators used in spin2
• Repair coloring of constant names used in array declarations
• Minor update to debug() statements: (1) allow in pasm, (2) don’t flag unknown names within debug()
• Repair recognition of org on DAT lines

- Known Issues w/v1.2.3

• debug() statements that don’t use double-quoted strings currently are not parsed correctly
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I’m sure there are more issues…

v1.2.2

Minor Highlighting Update - correctly colors binary operators in DAT data declarations

• fixed one case we missed.

- Known Issues w/v1.2.2

• debug() statements that don't use double-quoted strings currently are not parsed correctly
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

v1.2.1

Minor Highlighting Update - correctly colors binary operators in DAT data declarations

- Known Issues w/v1.2.1

• debug() statements that don't use double-quoted strings currently are not parsed correctly
• 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!!!!
• Occasional issues with highlighting of enum leading constant (#nnn should be recognized as number)
• I'm sure there are more issues...

Full Changelog: v1.2.0...v1.2.1