638
edits
No edit summary |
No edit summary |
||
Line 13: | Line 13: | ||
=== Replacing the DOM Binding with XPIDL Interfaces === | === Replacing the DOM Binding with XPIDL Interfaces === | ||
As noted above, we currently have two mechanisms for binding a script environment into Mozilla. The DOM binding uses generated C code to provide JavaScript-specific linkage, and was written to deal with the vagaries of the Level-0 JavaScript DOM. XPConnect uses a platform-independent ''type library'' with platform-specific method dispatch code to dynamically determine runtime binding. (footnote 1) | As noted above, we currently have two mechanisms for binding a script environment into Mozilla. The DOM binding uses generated C++ code to provide JavaScript-specific linkage, and was written to deal with the vagaries of the Level-0 JavaScript DOM. XPConnect uses a platform-independent ''type library'' with platform-specific method dispatch code to dynamically determine runtime binding. (footnote 1) | ||
The big first step towards supporting another scripting environment is to unify the current mechanisms used to integrate with JavaScript. This will involve a fair amount of work. | The big first step towards supporting another scripting environment is to unify the current mechanisms used to integrate with JavaScript. This will involve a fair amount of work. |
edits