- From: Arthur Barstow <art.barstow@nokia.com>
- Date: Tue, 10 Aug 2010 07:30:03 -0400
- To: public-script-coord <public-script-coord@w3.org>
-------- Original Message --------
Subject: [Bug 10336] New: "optional" should be allowed even if
subsequent arguments aren't optional
Date: Tue, 10 Aug 2010 00:28:52 +0200
From: ext bugzilla@jessica.w3.org <bugzilla@jessica.w3.org>
To: public-webapps@w3.org <public-webapps@w3.org>
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 Tuesday, 10 August 2010 11:30:43 UTC