W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2010

[Bug 10336] New: "optional" should be allowed even if subsequent arguments aren't optional

From: <bugzilla@jessica.w3.org>
Date: Mon, 09 Aug 2010 22:28:52 +0000
To: public-webapps@w3.org
Message-ID: <bug-10336-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10336

           Summary: "optional" should be allowed even if subsequent
                    arguments aren't optional
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: WebIDL
        AssignedTo: cam@mcc.id.au
        ReportedBy: ian@hixie.ch
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


It should be possible to say:

  void drawImage(in HTMLImageElement image, in float dx, in float dy, in
optional float dw, in float dh);

...so that it means the same as:

  void drawImage(in HTMLImageElement image, in float dx, in float dy);
  void drawImage(in HTMLImageElement image, in float dx, in float dy, in float
dw, in float dh);

Basically, have "optional" means that if the argument is omitted, all
subsequent ones must be too, but that if it is included, any subsequent
arguments up to the next "optional" must be included.

Currently, "optional" can't be omitted on arguments after the first with
"optional", so the above isn't possible.

-- 
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, 9 August 2010 22:28:53 GMT

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