Re : [css-variables] Putting it all toegether (syntax)

| On the other hand, some tools do implement this Core
| Grammar, like tinycss[1] (which throws when the input can't be parsed
| with the current grammar).

This is my point. When something is standardised, it get used. 
Breaking an unnecessary restriction is still breaking something.

Not to say we can't break it. Just that we shouldn't break it if it isn't useful.
It's yet to be seen if it's useful. This is where we are. As I stated in my
previous mail, I really would like to see the arguments that would help me
understand why this is useful. 



| > Thanks for citing a good reason not to use 'var' :-) If CSS variables
| > are not working like JS variables at all, I see no reason to make the
| > confusion between them possible. Anyway, if 'var' was going to be the
| > used prefix, I would not be upset about it. That's just not my first
| > choice (nor my second one), but I can deal with it easily.
| 
| What's your second choice than?

First choice was "my" but I like both "x" and "data" nearly as much. 

I think "var" (just like "let", "set" and "define") is too imperative and 
too few declarative. The 'set' operation and the 'declaration' are already
implied by the CSS declaration syntax (looks like JSON).



| I am not sure why you sound as if your summary/proposal isn't welcome.
| For what it's worth, I greatly appreciate your summary. Without it, I
| probably still think the $foo idea is about property replacement.

Not my point at all. I would just have preferred more actionable feedback and less
debate about the ideas I tried to include in the reflection. About those, it is, I fear, 
nearly impossible to reach a complete agreement. 

Endless debates are by definition unproductive.



| I would hope we have a wiki page for all the syntax variations people on
| this mailing list have come up, and reasons why some people like/dislike it.

Would be nice, indeed.

Received on Wednesday, 6 June 2012 08:16:11 UTC