Bug 117594 - Refactor ObjCCallbackFunction to allow use as both a function and a constructor
Summary: Refactor ObjCCallbackFunction to allow use as both a function and a constructor
Status: RESOLVED FIXED
Alias: None
Product: WebKit
Classification: Unclassified
Component: JavaScriptCore (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Mark Hahnenberg
URL:
Keywords:
Depends on: 117595
Blocks:
  Show dependency tree / graph
 
Reported: 2013-06-13 08:48 PDT by Mark Hahnenberg
Modified: 2014-02-06 10:47 PST (History)
0 users

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 Mark Hahnenberg 2013-06-13 08:48:50 PDT 
We want ObjCCallbackFunction to support being called as both a function and a constructor. Basically this means that ObjCCallbackFunction should have the functionality of both JSCallbackFunction and JSCallbackConstructor. To avoid having to use multiple inheritance, we need to make ObjCCallbackFunction implement its own versions of getCallData and getConstructData and keep track of its own callbacks.

This refactoring will be done in a series of patches. This is the tracking bug for those sub tasks.
Comment 1 Mark Hahnenberg 2014-02-06 10:47:38 PST 
Marking as fixed since ObjCCallbackFunction implements both getCallData and getConstructData now.