In some parts, you just swap one symbol/character with another, like class = type, h|gender = h.gender etc. Whether that impacts readability is personal preferences.
Changing the comparison operator may looks nice for now if you are just doing in/equality checks, but I'd still want that == as it also pairs with >= and <=.
The end; also seems redundant to me when you are still using the curly braces for blocks.
Finally, the deal breaker for me is the function syntax. I don't see any good reason to break function names and parameters into 2 lines and adding @args to denote what has already been perfectly describe by the traditional syntax function name(arg1, arg2). Also forcing lines to stick together is just as bad as Python's whitespace scope - and I hate that :P.
Or maybe I'm just too accustomed to the old ways and not seeing what you're offering :D
The point of swapping keywords and symbols is mostly for readability as the ones I added to StormScript either make more sense to me or make it more readable.
I believe that it is possible that
I could still use words rather than symbols for less than and greater than.
On end; being redundant I totally agree, and really just included it as a placeholder so that I can worry more about the core functionality. I am probably going to replace it with }; or just } in the next release.
I created @args: not because I like the look of it, but rather because of readability. I will change this at some point to something less likely to make code cluttered.
I think that one of my main issues with getting people to use StormScript is that it is different, but I won't let that stop me from changing common syntax to what I and hopefully my contributors will believe to be better.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
My opinions:
In some parts, you just swap one symbol/character with another, like
class=type,h|gender=h.genderetc. Whether that impacts readability is personal preferences.Changing the comparison operator may looks nice for now if you are just doing in/equality checks, but I'd still want that
==as it also pairs with>=and<=.The
end;also seems redundant to me when you are still using the curly braces for blocks.Finally, the deal breaker for me is the function syntax. I don't see any good reason to break function names and parameters into 2 lines and adding
@argsto denote what has already been perfectly describe by the traditional syntaxfunction name(arg1, arg2). Also forcing lines to stick together is just as bad as Python's whitespace scope - and I hate that :P.Or maybe I'm just too accustomed to the old ways and not seeing what you're offering :D
The point of swapping keywords and symbols is mostly for readability as the ones I added to StormScript either make more sense to me or make it more readable.
I believe that it is possible that
I could still use words rather than symbols for less than and greater than.
On
end;being redundant I totally agree, and really just included it as a placeholder so that I can worry more about the core functionality. I am probably going to replace it with};or just}in the next release.I created
@args:not because I like the look of it, but rather because of readability. I will change this at some point to something less likely to make code cluttered.I think that one of my main issues with getting people to use StormScript is that it is different, but I won't let that stop me from changing common syntax to what I and hopefully my contributors will believe to be better.