Cameron McCormack:
(Also I see that you’re using the “string” and “wstring”, and Lwide
string values. Are you of the opinion that Web IDL should introduce
those instead of DOMString?)
Shiki Okasaka:
In my opinion, it would be nice if we can use the keyword 'string' as
the same meaning of
Cameron McCormack c...@mcc.id.au wrote:
(Also I see that you’re using the “string” and “wstring”, and Lwide
string values. Are you of the opinion that Web IDL should introduce
those instead of DOMString?)
Shiki Okasaka sh...@google.com wrote:
In my opinion, it would be nice if we can use the
Hi,
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?
Max.
[1] http://dev.w3.org/2006/webapi/WebIDL/#prod-ConstExpr
Anne van Kesteren ann...@opera.com writes:
On Mon, 27 Apr 2009 15:56:42 +0200, Max Froumentin max...@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
Shiki, I notice that in your es-operating-system project you’re using
booleans and strings in consts, but just in the test suite. Do you need
these types in practice?
I think the use of string constants should be avoided to keep
specifications natural-language-neutral in practice even after
