You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Version Publicly Available Alpha: SugarCube v2.37.0-alpha.19+10193 Most Recent Build Available: SugarCube v2.37.0-alpha.20+1
I did not test the backported <<do>><<redo>> macro set for ≤ v2.36.1
Describe the bug.
Text within <<do>> macros may not be parsing comments properly. For instance, having <<do>> within a comment will trigger an error if used within a <<do>> macro.
To Reproduce:
:: APassageName
/* <<do>> */
<<do>>
No errors from comment outside of do macro!
<</do>>
<br><br>
<<do>>
Oh look, errors!
/* <<do>> */
<</do>>
Expected behavior.
No error.
Project details.
SugarCube Version: SugarCube v2.37.0-alpha.19+10193 and SugarCube v2.37.0-alpha.20+1
Included Add-ons: None
Included Libraries: None
Compiler & Version: Latest, Tweego, version 2.1.1+81d1d71 (2020-02-25T07:09:26Z) [windows/amd64]
Desktop details.
OS & Version: Windows 11
Browser & Version: Latest version of Firefox, Chrome and Edge
The text was updated successfully, but these errors were encountered:
Version
Publicly Available Alpha: SugarCube v2.37.0-alpha.19+10193
Most Recent Build Available: SugarCube v2.37.0-alpha.20+1
I did not test the backported
<<do>>
<<redo>>
macro set for ≤ v2.36.1Describe the bug.
Text within
<<do>>
macros may not be parsing comments properly. For instance, having<<do>>
within a comment will trigger an error if used within a<<do>>
macro.To Reproduce:
Expected behavior.
No error.
Project details.
Desktop details.
The text was updated successfully, but these errors were encountered: