@elif directive about engine

[wldcordeiro]

I wouldn't make it an alias, I'd change @else's behavior to be more in line with what else is in most languages. So ideally if would be the first condition and elif (or elsif or whatever way you like to name it) would be additional conditions and else would be the fall-back behavior if the if or elif blocks aren't true.

[appsforartists]

What's the difference between:

if {} elif {} else {}

and

if {} else {} else {}?

Two elses next to each other seems like nonsense unless the middle one is effectively elif. Since it's implemented that way now, the alias seems like a cheap fix.

[wldcordeiro]

@appsforartists Normally else doesn't accept conditions, it's basically a fall-back if no conditions are met so really the else in GSS is an elif and they need an else.

So instead of doing

if (condition) {
// foo
}
else (condition2) {
// bar
}
else (condition3) {
// baz
}

I think it should be

if (condition) {
// foo
}
elif (condition2) {
// bar
}
elif (condition3) {
// baz
}
else {
// blahblah
}

[appsforartists]

@wldcordeiro I see where you're coming from, I just don't see the importance of making a distinction between the two.

else (expression) { is already a supported syntax, so making that throw an error isn't nice to existing users. Aliasing else as elif accomplishes what you'd like (distinguishing between else and else if) without breaking backwards-compatibility.