W3C home > Mailing lists > Public > public-device-apis@w3.org > May 2011

Re: Important change in WebIDL (Was: [Bug 10640] Allow for non-nullable objects)

From: Rich Tibbett <richt@opera.com>
Date: Wed, 25 May 2011 14:11:26 +0200
Message-ID: <4DDCF1EE.7000608@opera.com>
To: Dominique Hazael-Massieux <dom@w3.org>
CC: public-device-apis@w3.org
Dominique Hazael-Massieux wrote:
> Hi,
>
> The Web IDL spec has just integrated a change that introduces a fairly
> big backward-incompatibility: up until now, the declaration
>          interface Foo {
>            attribute Bar myAttribute;
>          }
> implied that "null" was a valid value for myAttribute (since interface
> objects were always nullable).
>
> After the change described below, this is no longer the case, and
> nullability needs to be made explicit, à la
> 	interface Foo {
>            attribute Bar? myAttribute;
>          }
>
> (this applies as well to method arguments and return types)
>
> This like affects most of our APIs, and most certainly the Contacts API
> (which I now note is lacking the nullability marker on attributes of the
> Contact Interface)

I've updated the Contacts API to reflect this change in WebIDL syntax:

http://dev.w3.org/cvsweb/2009/dap/contacts/Overview.html.diff?r1=1.129;r2=1.130;f=h

- Rich
Received on Wednesday, 25 May 2011 12:11:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:14:20 GMT