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
This is because the "missing" colon is hard to recognise in current grammar, since I was lazy and the grammar is very broad. Any two expressions next to each other are allowed.
In the SQF something like this is valid with or without the colon:
so, as far as the grammar is concerned right now, it's the same as
private_arr= [1, 23, 4];
(the 3 is argument of command 2)
I know this is terrible. I'll need to create some kind of inteligent check whenever two expressions next to each other are callable or not. I'm thinking about making all the "operators" (commands) part of grammar, so the grammar correctly recognises these issues... that may take a while
And as far as the trailing colon, since when is that allowed? I feel like when I was making this extension, it produced error.
This does not produce error:
Additional colon is properly seen as error:
The text was updated successfully, but these errors were encountered: