W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [webidl] definition of const string literal

From: Max Froumentin <maxfro@opera.com>
Date: Mon, 27 Apr 2009 16:35:12 +0200
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "WebApps WG" <public-webapps@w3.org>
Message-ID: <m2tz4ab1wf.fsf@pc214.sm.oslo.opera.com>
"Anne van Kesteren" <annevk@opera.com> writes:

> On Mon, 27 Apr 2009 15:56:42 +0200, Max Froumentin <maxfro@opera.com>
> wrote:
>> The grammar in http://dev.w3.org/2006/webapi/WebIDL/ prevents
>> declarations such as:
>>
>> const DOMString foo = "bar";
>>
>> because the "ConstExp" rule [1] only allows a number, or "TRUE" or
>> "FALSE". Is it an omission?
>
> What is the use case? Web APIs usually work with numbers (if they have
> constants at all).

I was wondering that too. But if there are no use cases, then the spec should be changed to
disallow "const DOMString foo;". I'd disallow boolean too, in fact, but leave number constants.

Max.
Received on Monday, 27 April 2009 14:35:57 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT