- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Sat, 08 Jul 2017 23:45:53 +0000
- To: public-css-archive@w3.org
I'm intrigued by the idea of automatic concatenation of consecutive string tokens, but I'm worried that this might derail the general possibility of concatenation. I personally don't think one extra layer of function notation will create an overwhelming number of parentheses. But maybe I've just been programming too long. One thing I've mentioned elsewhere (and Lea seems to be assuming it, as well) is the idea that a concatenation function could do double-duty as a string coercion function, forcing any number or other non-string variables inside it into string version. This is very important for building SVG path data from variables. I'm worried that if you combine this with the default concatenation option you'd really make a mess of parsing. So my vote is for a `concat()` or `cat()` or `string()` function. And sooner rather than later. -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/542#issuecomment-313887828 using your GitHub account
Received on Saturday, 8 July 2017 23:45:59 UTC