W3C home > Mailing lists > Public > public-script-coord@w3.org > January to March 2012

Re: no longer treating explicit undefined as a missing, optional argument

From: Cameron McCormack <cam@mcc.id.au>
Date: Wed, 04 Jan 2012 12:50:43 +1100
Message-ID: <4F03B073.8000208@mcc.id.au>
To: Anne van Kesteren <annevk@opera.com>
CC: public-script-coord@w3.org
Anne van Kesteren:
> Where are [TreatUndefinedAs=Null] and [TreatUndefined=EmptyString] used?

I don't recall if they are being used currently.  If they aren't, we 
should remove them.

> Also, how do I keep the IDL readable? I guess I could define a special
> type.
> typedef LegacyString = [TreatUndefinedAs=Missing] DOMString?;
> Though that is still not really nice.

Banging these things into the IDL rather than being in the prose often 
comes at the price of being less readable.  I don't think

   void open(DOMString method, DOMString url, optional boolean async,
             [TreatUndefinedAs=Missing] optional DOMString? user,
             [TreatUndefinedAs=Missing] optional DOMString? password);

is completely unreadable.  You may like to format the extended 
attributes in your IDL fragments differently, so that they stand out 
less.  (I've never been a fan of the "only black text on silver 
background" IDL fragment formatting in specs.)
Received on Wednesday, 4 January 2012 01:53:40 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:05 UTC