I haven't revisited my P2 programs for almost a year now, but recently I wanted to do check on the code and after updating the extensions in VSC, I suddenly have lots of syntax errors, mostly on object methods, in a code that compiles ok. I tested in latest version of Spin Tools for comparison and it doesn't show any syntax errors there. I am using the latest version of flexspin as compiler. Did I miss some change I need to do with the new version of the Spin2 extension? Here's a screenshot for reference:
I haven't revisited my P2 programs for almost a year now, ..... Did I miss some change I need to do with the new version of the Spin2 extension?
For those of you reading this. I could not identify the cause but could not recreate the issue with the v2.2.15 as I was working on it before release. I then reviewed all the code, found and fixed 3 more issues I was able to find, and then pushed the new release.
Ok, I worked with @jrullan and found a defect in the handling of files on windows that was causing all of the object references to not be found.
I've just release v2.2.16 to address this issue.
Here's what's new in v2.2.16
v2.2.16
Update P2 Only
BUGFIX: Syntax: add missing bytefit/wordfit recognition in DAT blocks (#6)
BUGFIX: Semantic: repair handling of {Spin2_v??} built-in method name support
BUGFIX: File access issues on Windows (11?) repaired
Cleaned up the code-fold detection... now handling ORG* forms better (#6)
Adjusted report key chords for Windows:
Ctrl+Win+r - Generate Object Hierarchy Report
Ctrl+Win+d - Generate OBject Public Interface Report
Ctrl+Win+c - (When cursor on PUB or PRI line) Insert Doc comment below the PUB or PRI line
If you see any issues with these new features please let us know by filing new issues at our code repo. (or email me directly.)
I've just released version 2.3.0 of our spin2 extension. This is the first cut of a new compiler-independent build system.
Users of VSCode get automatic updates, so you all have these updates already!
Here's a recap of what's new in v2.2.17, v2.2.18, and v2.3.0
v2.2.18
Quick repackage and release to pull cruft out of distribution package (oops!)
v2.2.17
Update P2 Only
BUGFIX: parsing repair detection of alignl/alignw in VAR. Issue(#9)
Update P1 and P2
BUGFIX: FlexSpin support: implement new understanding. #include includes spin code but no longer needs spin/spin2 file extension. Issue(#11)
BUGFIX: FlexSpin support: fix highlighting for #include lines
v2.3.0
This update improves/simplifies the ability to compile and download code for Spin2 projects
NEW Automatic Toolchain discovery (paths for FlexProp, PNut, and pnut_ts are now automatically determined)
NEW Automatic PropPlug discovery
NEW statusBar control for switching between compile with debug() and without
NEW statusBar control for switching between download to FLASH / RAM
NEW statusBar control for selecting amongst available USB-attached PropPlugs
NEW Setting to select preferred compiler for all projects
NEW This setting can be overridden for each specific workspace (project)
NEW Setting to enable all this new spin2 toolchain support (disabled by default)
NEW Replacement User Tasks file is now universal (all supported compilers)
NOTE This release uses loadp2 from the flexspin installation to download code compiled by pnut_ts.
General Repairs
BUGFIX Repair crash when system-settings documents are open at startup
BUGFIX Spin2 Semantic Highlighting: fixed VAR section index coloring
Plan a time when you want to move to this new build support. Leave yourself an hour or two so you can do this setup carefully. Once set up, this will be fun to use!
This is our first release of this new build system. Please be sensitive to things being different. My goal is to make building and downloading much more simple than it previously was. But, since it is the first release, If you see any issues with these new features, please let us know by filing new issues at our code repo. (or email me directly.)
Upcoming With this finally being released, we can now move to adding highlighting support for Spin2 V45, v46, and v47... language features.
I've just released v2.3.1 followed by v2.3.2 of our spin2 extension. These fix the compiler detection code, in general, and additionally, path chasing on Windows.
Users of VSCode get automatic updates, so you all have these updates already!
Here's a recap of what's new:
v2.3.1 and v2.3.2
Repair parsing of PATH on windows and how expected location paths are created
Present Error if multiple installations are found for a given tool
Reduce search to unique paths (no dupes from PATH values)
Extension logging is enabled for now to help us diagnose new-user installations (it will be turned off once again in a later release)
I'll add a section on "How to verify the compiler search by using the newly exposed log" to our "Build System Notes" shortly...
This is our first release of this new build system. Please be sensitive to things being different. My goal is to make building and downloading much more simple than it previously was. But, since it is the first release, If you see any issues with these new features, please let us know by filing new issues at our code repo. (or email me directly.)
Upcoming With this finally being released, we can now move to adding highlighting support for Spin2 V45, v46, and v47... language features.
Comments
Stephen,
Just read your development over the past 18 months.
What you have achieved is nothing short of remarkable.
Congratulations!
Thank you! It's been fun to work on.
Thanks Stephen!!!
2.2.16 fixed my issue in Windows:
Ok, I worked with @jrullan and found a defect in the handling of files on windows that was causing all of the object references to not be found.
I've just release v2.2.16 to address this issue.
Here's what's new in v2.2.16
If you see any issues with these new features please let us know by filing new issues at our code repo. (or email me directly.)
NEWS
I've just released version 2.3.0 of our spin2 extension. This is the first cut of a new compiler-independent build system.
Users of VSCode get automatic updates, so you all have these updates already!
Here's a recap of what's new in v2.2.17, v2.2.18, and v2.3.0
Plan a time when you want to move to this new build support. Leave yourself an hour or two so you can do this setup carefully. Once set up, this will be fun to use!
Help with migration to this new mechanism is found at Migrate to v2.3.0 checklist with additional info found at Build System Notes.
This is our first release of this new build system. Please be sensitive to things being different. My goal is to make building and downloading much more simple than it previously was. But, since it is the first release, If you see any issues with these new features, please let us know by filing new issues at our code repo. (or email me directly.)
Upcoming With this finally being released, we can now move to adding highlighting support for Spin2 V45, v46, and v47... language features.
NEWS
I've just released v2.3.1 followed by v2.3.2 of our spin2 extension. These fix the compiler detection code, in general, and additionally, path chasing on Windows.
Users of VSCode get automatic updates, so you all have these updates already!
Here's a recap of what's new:
Help with migration to this new mechanism is found at Migrate to v2.3.0 checklist with additional info found at Build System Notes.
I'll add a section on "How to verify the compiler search by using the newly exposed log" to our "Build System Notes" shortly...
This is our first release of this new build system. Please be sensitive to things being different. My goal is to make building and downloading much more simple than it previously was. But, since it is the first release, If you see any issues with these new features, please let us know by filing new issues at our code repo. (or email me directly.)
Upcoming With this finally being released, we can now move to adding highlighting support for Spin2 V45, v46, and v47... language features.