cloudhead/less.js — comment on commit 624c297e7be093bd2234c4fac8d2bfa085cfadae
File:  line 0
By matthewdl:

Hmm...... The semi-colon as an ```or``` seems strange, since, again, it's established as a terminator. That plus a comma seems error-prone and confusion-ridden. Look at your example. As a developer, you have to take a minute to think about whether the line is terminating or it's the beginning of an ```or```. Then, I can see someone up late at night because they typed a comma instead of a semi-colon in a fourth-level deep LESS file, and didn't notice because commas and semi-colons look kinda similar. If you went that route, I think by not trying to make more to learn, you're actually making more to learn, because you're redefining what's already known, commas and semi-colons in the language. I'd rather see new keywords than re-definitions of existing ones, but that may be my personal preference. I'm a usability fanatic so, like I said, I like when things are not ambiguous. But, even preference aside, ```;``` for ```or``` seems like it could cause the most confusion of all the syntaxes thus far.

One other thing, were you thinking of supporting: condition ```(a and b) or c``` / ```(@a > 5, @b < 3); @c = 0```?

As far as a default mixin, I can see not wanting to do it, and instead forcing explicit matches, as long as you can sort of cover the use cases.