Bug 10713 - ObjC DOM auto-generation should honor the [Optional] attribute
Summary: ObjC DOM auto-generation should honor the [Optional] attribute
Status: RESOLVED CONFIGURATION CHANGED
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebKit API (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-09-03 13:20 PDT by Timothy Hatcher
Modified: 2017-06-16 22:20 PDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Timothy Hatcher 2006-09-03 13:20:59 PDT 
ObjC can do this by making as many methods as needed, one with the optional parameter and one without. This is more complex when there are multiple [Optional] parameters. We will need to step up through the optional parameters making a new method as we add one to the end.
Comment 1 David Kilzer (:ddkilzer) 2006-09-03 14:21:07 PDT 
For what it's worth, when I added support for the [Optional] parameter in CodeGeneratorJS.pm, the first argument marked [Optional] in the args list would make all subsequent args (to the right) implicitly optional (even without the [Optional] designation) since JavaScript has neither strongly-typed nor named parameters.  This is the way it's currently implemented in CodeGeneratorJS.pm.
Comment 2 mitz 2017-06-16 22:20:30 PDT 
The Objective-C DOM API is not being generated automatically anymore.