We've just released v1.52.2; we've improved performance where we can.
Here's what's new/fixed:
v1.52.2
Improved performance
Several small changes to the code allow us to compile faster (I'm seeing ~1.9x to ~2x), but this depends on the style of your code. Your mileage may vary.
We do comprehensive regression testing in preparation for each release. We also add to our regression suite to test all new capabilities. You can review our coverage testing via regress at PNut-TS Coverage Testing
If you spot any issues with code generation or compilation, you can review the testing process. This should help you identify differences between PNut v52a and PNut_TS v1.52.2.
We look forward to hearing what you find.
As always, you can report issues here, or, better yet, if fixes are needed, report problems on the repository issues page. (You can also see the current list of what's been reported at this page.)
Language: OFFSETOF(struct.member) compile-time function — returns byte offset of a member within a structure definition
Language: Support for {Spin2_v53} language version directive
CLI: Allow filename without .spin2 extension — resolves to .spin2 if file exists in current directory
Fixed
Language: CASE block colon parsing now validates colon token (3 locations changed from get_element to get_colon)
BUGFIX: Fixed {Spin2_v##} version tag not being detected when preceded by blank lines after header comments. Files with comment blocks followed by a blank line before the version tag would silently default to v41, causing keywords like STRUCT and SIZEOF to go unrecognized
BUGFIX: Fixed off-by-one error in inline {...} comment handling within the elementizer. Non-doc comments embedded mid-line (e.g., long {old_value}$FF0000) would eat the first character after the closing }, producing cryptic "Undefined symbol" errors
Diagnostics: When a version-gated keyword is used without the required language version, the compiler now reports "STRUCT" requires {Spin2_v45} or later instead of the misleading Expected "=" "[" "," or end of line
We do comprehensive regression testing in preparation for each release. We also add to our regression suite to test all new capabilities. You can review our coverage testing via regress at PNut-TS Coverage Testing
If you spot any issues with code generation or compilation, you can review the testing process. This should help you identify differences between PNut v53 and PNut_TS v1.53.0.
We look forward to hearing what you find.
As always, you can report issues here, or, better yet, if fixes are needed, report problems on the repository issues page. (You can also see the current list of what's been reported at this page.)
Comments
Hi @"Stephen Moraco",
Just some more info on this issue:
I am running on the latest Debian 13 Trixie but also see the same on Fedora 42 and Debian 12
I can run from command line but would really like to understand the VSCODE situation.
I appreciate your tremendous work in the propeller community and understand you are juggling many things !
Thanks
Bob
NEWS
We've just released v1.52.2; we've improved performance where we can.
Here's what's new/fixed:
PNut-TS is found at its Public Repository, while the latest Releases are also found there at the Releases Page
We do comprehensive regression testing in preparation for each release. We also add to our regression suite to test all new capabilities. You can review our coverage testing via regress at PNut-TS Coverage Testing
If you spot any issues with code generation or compilation, you can review the testing process. This should help you identify differences between PNut v52a and PNut_TS v1.52.2.
We look forward to hearing what you find.
As always, you can report issues here, or, better yet, if fixes are needed, report problems on the repository issues page. (You can also see the current list of what's been reported at this page.)
Stephen & Chip
NEWS
We've just released v1.53.0. (PNut v53 parity)
Here's what's new/fixed:
PNut-TS is found at its Public Repository, while the latest Releases are also found there at the Releases Page
We do comprehensive regression testing in preparation for each release. We also add to our regression suite to test all new capabilities. You can review our coverage testing via regress at PNut-TS Coverage Testing
If you spot any issues with code generation or compilation, you can review the testing process. This should help you identify differences between PNut v53 and PNut_TS v1.53.0.
We look forward to hearing what you find.
As always, you can report issues here, or, better yet, if fixes are needed, report problems on the repository issues page. (You can also see the current list of what's been reported at this page.)
Stephen & Chip