W3C home > Mailing lists > Public > www-style@w3.org > April 2013

Re: [css-variables][naming] Renaming 'var'

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Sun, 14 Apr 2013 02:06:59 +0200
To: Sylvain Galineau <galineau@adobe.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <79rjm8h5dgsirve9llgibatkicr9t883qu@hive.bjoern.hoehrmann.de>
* Sylvain Galineau wrote:
>On 4/13/13 3:57 PM, "Bjoern Hoehrmann" <derhoermi@gmx.net> wrote:
>>* fantasai wrote:
>>>So, at Rename the Web Forward [1], Sylvain and I concluded that it
>>>just might be better to use 'set-' as the prefix and 'get()' as the
>>>function name instead of 'var-' and 'var()'.

>>Well, `get` and `set` as used here are imperative, while CSS tries to be
>>a declarative language, so this seems rather confusing to me.

>What, specifically, would an end-user be confused about and how would this
>confusion manifest itself?  

The `var-` prefix exists only because a namespacing mechanism is needed
to avoid clashes between pre-defined and author-defined properties. The
`set-` prefix conveys that even less than `var-`. We call `color: blue`
a declaration, but `set` does not "declare", it "sets"; obviously there
would be a reason why the designers of this syntax chose "set" as name,
rather than something with more declarative semantics, so custom proper-
ties work differently than normal properties. Obviously `get` would get
the value associated with the name when it was last `set`, and "when" is
temporal, so in order to understand what value `get` retrieves, I have
to understand the execution order of the `set` instructions...
-- 
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Am Badedeich 7 · Telefon: +49(0)160/4415681 · http://www.bjoernsworld.de
25899 Dagebüll · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Sunday, 14 April 2013 00:07:24 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:10 UTC