[BUG] sksp compiler syntax not fully supported

[nodzsound]

Describe the bug

sksp allows you to add the variable that activates a USE_CODE statement to the start AND the end of a code block. cksp does not support the variable for the END_USE_CODE statement.

To Reproduce

USE_CODE(TEST_VARIABLE)
   x := 1
END_USE_CODE(TEST_VARIABLE)

CKSP Version

0.0.8

Operating System

Windows

OS Architecture

x86_64

Tooling

• Using VS Code plugin
• Using Sublime Text build system

[mathiasvatter]

funnily enough, I do not think adding the variable to END_USE_CODE is a feature in sksp, it seems more like a regular expression mistake :D It does not check at all if the variable put after END_USE_CODE is in fact the variable that was given USE_CODE_IF. In fact, it does not seem to check for anything that comes after END_USE_CODE. For sksp, this is perfectly valid code:

on init
	SET_CONDITION(BLABLA)
	USE_CODE_IF(BLABLA)
	declare i
	END_USE_CODE.....whatishappening(-------)()-------sdflkajydlkwhfakhrv
	for i := 0 to 40
		message(i)
	end for
end on

so if users of sksp can just write anything after END_USE_CODE I am not really sure what to implement in cksp here :D

[nodzsound]

Depends on how compatible you want to be with sksp and how heavy you want to enforce the cksp style. You can keep things as is and enforce that END_USE_CODE has to be the full line or you can copy the sksp behavior and ignore anything that comes after. :)