W3C home > Mailing lists > Public > public-script-coord@w3.org > October to December 2011

[Bug 14878] Rename const to legacyconst

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Nov 2011 17:39:09 +0000
To: public-script-coord@w3.org
Message-Id: <E1RSXpl-00061c-Tl@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14878

Travis Leithead [MSFT] <travil@microsoft.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |travil@microsoft.com

--- Comment #3 from Travis Leithead [MSFT] <travil@microsoft.com> 2011-11-21 17:39:09 UTC ---
(In reply to comment #0)
> You always want to use string literals instead.

Is this referring to string literals assigned to const properties, or are you
simply saying that const was a bad idea, and in general shouldn't be used
anymore in future APIs?

There are certainly some advantages to having numerical constants, especially
for APIs that can have overlapping state (like compareDocumentPosition, or
mouseevent.buttons) and use a number as a bit mask.

I think this "problem" might be better solved by some WebIDL recommended best
practices for const, rather than flagging all const properties as "legacy" (do
not use).

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 21 November 2011 17:39:11 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:05 UTC