Setting the comment to this will prevent PlayerElim from being picked up as a function if an ‘=’ sign is present on the same line as an IF Statement
if (PlayerCounted = 0.00): #=
EndGame.Activate(Player)
Logger.Print("Game Ending via Verse")
#Scoring
PlayerElim(Player:player):void=
Hi @SnowSoftServe, do you mind posting the full Verse snippet that you have and the compiler error(s) from the log? Also, to clarify, are you saying that PlayerElim does not get recognized as a symbol when you have the #= comment in that code block above? (i.e. if you just remove the #= text, the code then parses without issues?)
Currently not home for the next few days, but once I’m home, I’ll send over the entire verse snippet! But what I was running into was if I had the #= in the same line as an If statement, the PlayerElim line isn’t getting recognized as a function (highlighted in blue text vs. yellow text)
the PlayerElim line isn’t getting recognized as a function (highlighted in blue text vs. yellow text)
Ok, I think I understand what you’re running into: the compiler actually still does parse your code correctly, so you don’t have to worry about this causing any errors; your function is still being recognized and will not cause any compilation issues… What you’re seeing is that the Visual Studio Code extension is not performing the syntax highlighting correctly, which I can reproduce with an isolated example:
a:int = 5
foo():void=
if (a = 0): # the presence of the `=` token anywhere in this comment after the `if` statement breaks syntax highlighting for any definition after
b:int = 10
testfoo():void=
return
Thanks for the report. We’ll take a look at addressing this. That said, If you do run into any other errors during compilation, please do share them (along with the original snippet) at your earliest convenience; we’d be very interested in fixing those.
Awesome sonictke, thank you!